https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46981
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #0)
> config-ml.in adjusts LD_LIBRARY_PATH for multilib target libraries. This
> apparently was introduced to ensure that applications created by configure
> in multilib directories find the correct libraries:
>
> http://gcc.gnu.org/ml/gcc-patches/2000-08/msg00666.html
>
> However, GCC cc1 now relies on libstdc++ via libppl and LD_LIBRARY_PATH will
> specify the 64 bit directory for the 64 bit multilib of a target library:
>
> /tmp/201012005/powerpc-ibm-aix5.3.0.0/ppc64/libstdc++-v3/src/.libs
>
> If libstdc++-v3 is configured and built before libgfortran, for example, 64
> bit libgfortran configure will fail because 32 bit cc1 finds the wrong
> version of libstdc++-v3. LD_LIBRARY_PATH is affecting the host path, not
> only the target path.
>
> I am not sure why this started to fail on AIX now (timing issue?), but it
> causes a bootstrap failure of target libraries.
I thought gcc didn't use libppl any longer?
