[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 --- Comment #20 from Denis Excoffier Denis.Excoffier at airbus dot com 2011-01-03 15:33:08 UTC --- I confirm that it is fixed in 4.5.2.
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 --- Comment #19 from Vincent Lefèvre vincent at vinc17 dot org 2010-12-12 23:02:58 UTC --- FYI, the problem has been handled in the MPFR trunk r7291 for MPFR 3.1.0. MPFR's configure script now retrieves the location of the GMP source from GMP's Makefile and adds the necessary -I... flags to CPPFLAGS. Note also that the behavior will be different from the one with MPFR 2.x. A side effect is that library versioning is not supported in this case (by that, I mean that a GMP upgrade without recompiling MPFR against the new GMP version may break things) because providing --with-gmp-build makes the MPFR build use GMP's internals, which may change without notice.
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 Andreas Beckmann gcc at abeckmann dot de changed: What|Removed |Added CC||gcc at abeckmann dot de --- Comment #18 from Andreas Beckmann gcc at abeckmann dot de 2010-11-03 09:08:14 UTC --- Is there a chance to get this trivial fix backported to 4.4 and 4.3, too?
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added CC||samsonluk at gmail dot com --- Comment #15 from Richard Guenther rguenth at gcc dot gnu.org 2010-10-06 10:26:21 UTC --- *** Bug 45905 has been marked as a duplicate of this bug. ***
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|--- |4.5.2 --- Comment #17 from Richard Guenther rguenth at gcc dot gnu.org 2010-10-06 10:30:18 UTC --- Fixed for 4.5.2.
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455 --- Comment #16 from Richard Guenther rguenth at gcc dot gnu.org 2010-10-06 10:29:58 UTC --- Author: rguenth Date: Wed Oct 6 10:29:55 2010 New Revision: 165020 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=165020 Log: 2010-10-06 Richard Guenther rguent...@suse.de Backport from mainline 2010-07-23 Marc Glisse marc.gli...@normalesup.org PR bootstrap/44455 * configure.ac (extra_mpfr_configure_flags): Copy from extra_mpc_gmp_configure_flags. * configure: Re-generated. Modified: branches/gcc-4_5-branch/ChangeLog branches/gcc-4_5-branch/configure branches/gcc-4_5-branch/configure.ac
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #13 from rguenth at gcc dot gnu dot org 2010-07-23 19:35 --- Subject: Bug 44455 Author: rguenth Date: Fri Jul 23 19:35:24 2010 New Revision: 162482 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=162482 Log: 2010-07-23 Marc Glisse marc.gli...@normalesup.org PR bootstrap/44455 * configure.ac (extra_mpfr_configure_flags): Copy from extra_mpc_gmp_configure_flags. * configure: Re-generated. Modified: trunk/ChangeLog trunk/configure trunk/configure.ac -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #14 from rguenth at gcc dot gnu dot org 2010-07-23 19:35 --- Committed to trunk. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Known to work||4.6.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #8 from bonzini at gnu dot org 2010-07-13 09:32 ---
Yes, C-only bootstrap is enough.
Regarding the removal of an installed GMP, in theory yes, it would be
preferable. In practice removing it would force you to use an old bootstrap
GCC that does not use MPC/MPFR/GMP, and there is an easy way to check that the
right library is used for the build, so it is not necessary. Since in-tree
GMP/MPFR are statically linked, just do ldd *gcc/cc1 in the build directory,
and check that it doesn't include any relevant GMP/MPFR/MPC shared library.
For smoke testing, just compile a simple int main() {} file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #9 from marc dot glisse at normalesup dot org 2010-07-13 14:26 --- Ok, the 4 tests worked fine. I tested with gcc-4.5.0 because the snapshots complained about the number of arguments to ggc_alloc_cleared_lang_type (without any patch). I used --without-ppl (otherwise you get gmp through it). MPC was in-tree for all tests for the same reason. ldd on cc1 never showed mpfr, and only showed libgmp.so.3 when it was out of tree. strings on cc1 also confirmed that the right one was used (the system versions of gmp and mpfr are different from the one I tested in-tree). The versions of mpfr I tested are the latest (3.0.0) and the oldest on which configure only warns and doesn't fail (2.3.1). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #10 from bonzini at gnu dot org 2010-07-13 14:43 --- Great! Do you have commit rights? Patch is ok for all 4.5 and 4.6. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #11 from marc dot glisse at normalesup dot org 2010-07-13 15:01 --- Sorry, no commit rights. I wrote the patch because it was a one-liner, but I still don't even have a copyright assignment on file. Can you handle the rest? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #12 from bonzini at gnu dot org 2010-07-13 15:31 --- Subject: Re: GCC fails to build if MPFR 3.0.0 (Release Candidate) is used On 07/13/2010 05:01 PM, marc dot glisse at normalesup dot org wrote: --- Comment #11 from marc dot glisse at normalesup dot org 2010-07-13 15:01 --- Sorry, no commit rights. I wrote the patch because it was a one-liner, but I still don't even have a copyright assignment on file. Can you handle the rest? Yep, but I'm on holiday so no hurry. :) Paolo -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #7 from marc dot glisse at normalesup dot org 2010-07-12 20:34 --- (In reply to comment #5) The patch is okay, but it should be tested with bootstrap, `make install' and a smoke test after install with: - in-tree GMP, in-tree MPFR 2.3 - in-tree GMP, in-tree MPFR 3.0 - out-of-tree GMP, in-tree MPFR 2.3 - out-of-tree GMP, in-tree MPFR 3.0 Is it enough to test with --enable-languages=c? What is a smoke test, gcc -v? Does it matter if the system has gmp and mpfr installed, even when doing the in-tree tests (I hope not, because I won't remove them)? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #6 from a dot heider at gmail dot com 2010-07-11 11:17 --- 4.4.4 is affected as well -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #5 from bonzini at gnu dot org 2010-07-08 16:24 --- The patch is okay, but it should be tested with bootstrap, `make install' and a smoke test after install with: - in-tree GMP, in-tree MPFR 2.3 - in-tree GMP, in-tree MPFR 3.0 - out-of-tree GMP, in-tree MPFR 2.3 - out-of-tree GMP, in-tree MPFR 3.0 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #4 from marc dot glisse at normalesup dot org 2010-07-07 07:44 --- Created an attachment (id=21121) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21121action=view) Trivial patch There doesn't seem to be much point using --with-gmp-build (it is mostly useful to improve performance a bit, but gcc explicitly tells GMP to be slow), so let's just use the same options as MPC. It works with mpfr 2.3.1 and 3.0.0. Any particular trap I am missing? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #2 from nightstrike at gmail dot com 2010-06-14 17:35 --- I can confirm this as a valid bug, but I don't have the bugzilla permissions to do so. Can someone update this to New? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #3 from froydnj at gcc dot gnu dot org 2010-06-14 17:51 --- Switched to NEW for NightStrike. -- froydnj at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2010-06-14 17:51:22 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
[Bug bootstrap/44455] GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
--- Comment #1 from Denis dot Excoffier at airbus dot com 2010-06-11 08:05 --- The same applies to mpfr-3.0.0 (now official). The MPFR people have however added the following note in ./INSTALL: As gmp-impl.h and longlong.h are only in the GMP source directory, you first need to copy these files to the build directory if it is different (there may be other workarounds, such as setting $CPPFLAGS to search the GMP source directory). This may be a better workaround than the one i proposed first. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
