[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #1 from Volker Braun --- Created attachment 33770 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33770&action=edit Log of the MPIR compilation ending in the testsuite failure
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #3 from Volker Braun --- Created attachment 33773 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33773&action=edit gdb log of the failing testcase
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #2 from Volker Braun --- Created attachment 33771 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33771&action=edit gcc -v output
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610
--- Comment #4 from Volker Braun ---
I got my hands on a gcc 4.9.1 binary build made on OSX 10.9 and this one works.
Diffing the log shows that this is due to different linker flags, my binary
build calls
libtool: link: gcc -std=gnu99 -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o
.libs/libmpir.11.dylib [...]
whereas the Yosemite-bootstrapped gcc calls
libtool: link: gcc -std=gnu99 -dynamiclib -Wl,-flat_namespace -Wl,-undefined
-Wl,suppress -o .libs/libmpir.11.dylib [...]
Relinking with the previous linker flags fixes the segfault. This is most
likely due to incorrect aclocal.m4 case check
case ${MACOSX_DEPLOYMENT_TARGET-10.0},$host in
10.0,*86*-darwin8*|10.0,*-darwin[[91]]*)
_lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
10.[[012]]*)
_lt_dar_allow_undefined='${wl}-flat_namespace ${wl}-undefined
${wl}suppress' ;;
not taking 10.10 properly into account.
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #5 from Volker Braun --- Libtool upstream patch: ​http://lists.gnu.org/archive/html/libtool-patches/2014-09/msg2.html
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 howarth at bromo dot med.uc.edu changed: What|Removed |Added CC||howarth at bromo dot med.uc.edu --- Comment #6 from howarth at bromo dot med.uc.edu --- Created attachment 33817 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33817&action=edit convenience patch
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610
--- Comment #7 from howarth at bromo dot med.uc.edu ---
I can confirm that there are many regressions (particularly in the fortran test
suite) on Yosemite due to the libtool bug which causes shared libraries to be
linked as if the target was Puma. The attached convenience patch solves the
issue (which should only be triggered if MACOSX_DEPLOYMENT_TARGET is being
set). The fix is of the form...
Index: gcc-4.9.1/gcc/configure
===
--- gcc-4.9.1.orig/gcc/configure
+++ gcc-4.9.1/gcc/configure
@@ -14415,7 +14415,7 @@ $as_echo "$lt_cv_ld_force_load" >&6; }
case ${MACOSX_DEPLOYMENT_TARGET-10.0},$host in
10.0,*86*-darwin8*|10.0,*-darwin[91]*)
_lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
- 10.[012]*)
+ 10.[012][,.]*)
_lt_dar_allow_undefined='${wl}-flat_namespace ${wl}-undefined
${wl}suppress' ;;
10.*)
_lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #8 from Volker Braun --- Another workaround is to set MACOSX_DEPLOYMENT_TARGET=10.9 Libtool-2.4.3 will have the fix, gcc (and everybody else) should just reconfigure when its out. http://lists.gnu.org/archive/html/libtool/2014-10/msg1.html
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #9 from howarth at bromo dot med.uc.edu --- Alternatively, you can just make sure you don't set MACOSX_DEPLOYMENT_TARGET in your shell. Also mote that gmp, mpfr and mpc also suffer from this bug and, if built on 10.10, should either have their configure scripts patched or regenerated with the fixed libtool.
[Bug target/63610] OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610 --- Comment #10 from howarth at bromo dot med.uc.edu --- (In reply to Volker Braun from comment #8) > Another workaround is to set MACOSX_DEPLOYMENT_TARGET=10.9 > > Libtool-2.4.3 will have the fix, gcc (and everybody else) should just > reconfigure when its out. > > http://lists.gnu.org/archive/html/libtool/2014-10/msg1.html Libtool 2.4.3 was released on Oct 27th. There should be a 2.4.4 released with a week, http://lists.gnu.org/archive/html/bug-libtool/2014-10/msg9.html, to eliminate http://lists.gnu.org/archive/html/bug-libtool/2014-10/msg6.html. Upstream contends that this bug is limited to the libtool installation and isn't transmitted beyond.
