https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #12 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #7)
> /usr/bin/ld:
> /tmp/OBJDIR/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6:
> version `GLIBCXX_3.4.30' not found (required by /usr/bin/ld)
>
>
> The problem is not realted to GCC directly but rather ld being linked
> against a newer version of libstdc++ and now you just compiled an older
> version of libstdc++ and that is in the LD_LIBRARY_PATH some how ... Which
> should not happen ....
Could libtool be erroneously populating LD_LIBRARY_PATH?
> If anything this should be reported to binutils and have ld (I suspect gold
> here) use -static-libstdc++ -static-libgcc while linking just the same way
> GCC does.
No, this doesn't make sense, ld shouldn't work around wrong LD_LIBRARY_PATH
setting.
