complibs/mpc: fix MPC 0.8.1 build with MPFR 3.0.0
This is the change introduced by revision 734 of MPC repository.
Author: Paul Zimmermann <Paul.Zimmermann@loria.fr>
Revision log: [acos.c] fixed problem with GMP_RNDA (should be MPFR_RNDA, and code was wrong)
Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>
1 config CC_GCC_ENABLE_TARGET_OPTSPACE
3 prompt "Optimize gcc libs for size"
6 Pass --enable-target-optspace to crossgcc's configure.
8 This will compile crossgcc's libs with -Os.
10 config CC_STATIC_LIBSTDCXX
12 prompt "Link libstdc++ statically into the gcc binary"
14 depends on CC_GCC_4_4_or_later
16 Newer gcc versions use the PPL library which is C++ code. Statically
17 linking libstdc++ increases the likeliness that the gcc binary will
18 run on machines other than the one which it was built on, without
19 having to worry about distributing the matching version of libstdc++
22 comment "Misc. obscure options."
26 prompt "Use __cxa_atexit"
28 depends on ! BARE_METAL
30 If you get the missing symbol "__cxa_atexit" when building C++ programs,
31 you might want to try disabling this option.
33 config CC_GCC_DISABLE_PCH
35 prompt "Do not build PCH"
38 Say 'y' here to not use Pre-Compiled Headers in the resulting toolchain.
39 at the expense of speed when compiling C++ code.
41 For some configurations (most notably canadian?), PCH are broken, and
42 need to be disabled. Please see:
43 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40974
45 config CC_GCC_SJLJ_EXCEPTIONS
47 prompt "Use sjlj for exceptions"
48 depends on ! BARE_METAL
51 'sjlj' is short for setjmp/longjmp.
53 On some architectures, stack unwinding during exception handling
54 works perfectly well without using sjlj, while on some others,
55 use of sjlj is required for proper stack unwinding.
57 Option | sjlj use | Associated ./configure switch
58 ---------+--------------------+--------------------------------
59 Y | forcibly used | --enable-sjlj-exceptions
60 M | auto | (none, ./configure decides)
61 N | forcibly not used | --disable-sjlj-exceptions
63 It should be safe to say 'M' or 'N'.
65 It can happen that ./configure is wrong in some cases. Known
66 case is for ARM big endian, where you should say 'N'.
68 config CC_GCC_LIBMUDFLAP
70 prompt "Compile libmudflap"
73 libmudflap is a pointer-use checking tool, which can detect
74 various mis-usages of pointers in C and (to some extents) C++.
76 You should say 'N' here, as libmduflap generates instrumented
77 code (thus it is a bit bigger and a bit slower) and requires
78 re-compilation and re-link, while it exists better run-time
79 alternatives (eg. DUMA, dmalloc...) that need neither re-
80 compilation nor re-link.