public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/46981] New: multilib LD_LIBRARY_PATH prevents configuration of target libraries
@ 2010-12-16 16:59 dje at gcc dot gnu.org
2012-03-22 3:00 ` [Bug bootstrap/46981] " dje at gcc dot gnu.org
2021-09-02 2:07 ` amodra at gmail dot com
0 siblings, 2 replies; 3+ messages in thread
From: dje at gcc dot gnu.org @ 2010-12-16 16:59 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46981
Summary: multilib LD_LIBRARY_PATH prevents configuration of
target libraries
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dje@gcc.gnu.org
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/46981] multilib LD_LIBRARY_PATH prevents configuration of target libraries
2010-12-16 16:59 [Bug bootstrap/46981] New: multilib LD_LIBRARY_PATH prevents configuration of target libraries dje at gcc dot gnu.org
@ 2012-03-22 3:00 ` dje at gcc dot gnu.org
2021-09-02 2:07 ` amodra at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: dje at gcc dot gnu.org @ 2012-03-22 3:00 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46981
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-03-22
CC| |dje at gcc dot gnu.org
Ever Confirmed|0 |1
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug bootstrap/46981] multilib LD_LIBRARY_PATH prevents configuration of target libraries
2010-12-16 16:59 [Bug bootstrap/46981] New: multilib LD_LIBRARY_PATH prevents configuration of target libraries dje at gcc dot gnu.org
2012-03-22 3:00 ` [Bug bootstrap/46981] " dje at gcc dot gnu.org
@ 2021-09-02 2:07 ` amodra at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: amodra at gmail dot com @ 2021-09-02 2:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46981
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #3 from Alan Modra <amodra at gmail dot com> ---
This is more than just an AIX problem. Use of LD_LIBRARY_PATH prevents
bootstrapping with any tools that happen to use libstdc++.so, for example,
ld.gold on Linux. If the new libstdc++.so is incompatible with the version
ld.gold was linked against the result is typically a segfault on ld.gold
startup, when attempting to build gcc stage3 target libraries. A workaround is
to install a statically compiled ld.gold.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-09-02 2:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-16 16:59 [Bug bootstrap/46981] New: multilib LD_LIBRARY_PATH prevents configuration of target libraries dje at gcc dot gnu.org
2012-03-22 3:00 ` [Bug bootstrap/46981] " dje at gcc dot gnu.org
2021-09-02 2:07 ` amodra at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).