[Bug target/97865] libtool needs to be updated for Darwin20.
iains at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Nov 19 12:53:18 GMT 2020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865
--- Comment #18 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #17)
> Iain, as I wrote below your changes seem not sufficient, I will recheck when
> I build your branch with gmp/mpfr/mpc built with dynamic_lookup, but it
> seems that there are some things where you missed the dynamic_lookup.
OK - we need to figure out what's different in the setups (I don't get the same
result)
-----
* I found that there was one incorrect case in libgfortran (where there is a
direct reference to **environ from the dylib, which is not allowed) - this was
being hidden by the 'global dynamic_lookup' -- the master-wip-config-darwin20
branch has a patch now for that too.
My test setup
clean install of macOS11.0.1
master-wip-config-darwin20
command line install of XC12.2RC
GMP/MPFR/PMC/ISL are built in-tree (the sources are symlinked into the root
dir)
/src-local/gcc-master/configure
--prefix=/opt/iains/x86_64-apple-darwin20/gcc-11-0-0
--target=x86_64-apple-darwin20 --host=x86_64-apple-darwin20
--build=x86_64-apple-darwin20
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
--enable-languages=all CC=x86_64-apple-darwin19-gcc
CXX=x86_64-apple-darwin19-g++
^^^ My bootstrap compiler is x86_64-apple-darwin19 gcc-7.5 (with Ada because of
enable-languages=all)
I have build logs, install logs and test logs, none of these are showing any
error.
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes 55631
# of expected failures 232
# of unsupported tests 82
/scratch/11-0-sur/gcc-master/gcc/gfortran version 11.0.0 20201118
(experimental) [master-wip-config-darwin20 revision r11-5152-gb57eea8b1d7d]
(GCC)
====
The effort of testing a top-level configuration change across multiple
platforms is quite significant - so I'd rather not hack a minimal change and
then have to go back and fix it properly later - so let's get to the bottom of
what's happening and find the correct solution.
More information about the Gcc-bugs
mailing list