Bug 29950 - gcc-config doesn't allow multiple library paths in LDPATH=
Bug#: 29950 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: toolchain@gentoo.org Reported By: brad@mainstreetsoftworks.com
Component: GCC Porting
URL: 
Summary: gcc-config doesn't allow multiple library paths in LDPATH=
Keywords:  
Status Whiteboard: 
Opened: 2003-09-29 13:55 0000
Description:   Opened: 2003-09-29 13:55 0000 
Basically because of a 
if [ -d "${LDPATH}" ]
statement, it doesn't allow an LDPATH like this:
LDPATH="dir1:dir2:dir3"
yet, LDPATH parameters in /etc/env.d _do_ allow that.
This is a patch to comment out that restriction.  This is
required for a GCC patch I'm about to submit for multilib support
for GCC on amd64

------- Comment #1 From Brad House 2003-09-29 13:56:49 0000 ------- 
Created an attachment (id=18500) [details]
patch to allow multiple paths LDPATH when using gcc-config

------- Comment #2 From Brad House 2003-10-18 12:45:08 0000 ------- 
gcc-config-1.3.3-r2  has these changes needed for gcc-3.3.1-r5 for
amd64

------- Comment #3 From Travis Tilley (RETIRED) 2004-05-05 13:54:19 0000 ------- 
*** Bug 50132 has been marked as a duplicate of this bug. ***

------- Comment #4 From Travis Tilley (RETIRED) 2004-05-05 13:55:33 0000 ------- 
ok, it seems this bug now applies to all archs and not just amd64. since i am
on an amd64 box, i never even noticed a problem.. since we seem to already have
a fix.

------- Comment #5 From Martin Schlemmer (RETIRED) 2004-05-06 11:56:42 0000 ------- 
Stupid question - does it have the entries in the correct order in ld.so.conf?

------- Comment #6 From SpanKY 2004-05-06 17:45:14 0000 ------- 
fixed in cvs

------- Comment #7 From Travis Tilley (RETIRED) 2004-05-06 23:32:48 0000 ------- 
martin - from my ld.so.conf:

/usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3
/usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3
/usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.0

(i have 3.3.3 and 3.4.0 installed at the moment)

same order regardless of which compiler is active. yeah... i'd say that's a bug.

------- Comment #8 From Martin Schlemmer (RETIRED) 2004-05-07 13:47:16 0000 ------- 
Yeah, some nut in portage dev decided that the order in env.d doesn't bother
him, and went and sorted it.  Might be mistaken though, but I want to remember
it did not do it in the past (and why my gcc2/gcc3 installation did the
right thing at the time, before I wiped it).

Can anybody in portage dev confirm that ld.so.conf entries was not always
sorted?  This is also sorda a sticky issue with mozilla/firefox/etc.

------- Comment #9 From Martin Schlemmer (RETIRED) 2004-05-08 07:29:00 0000 ------- 
Oh, and could we add it in the order it appears in /etc/env.d/ ?

------- Comment #10 From Nicholas Jones (RETIRED) 2004-05-16 04:05:05 0000 ------- 
Yeah... Looks like the sort has been in since at least October...
It's in every version since 2.0.49-r15, at least.

It's not present in any portage-2.0.51.

------- Comment #11 From Martin Schlemmer (RETIRED) 2004-06-20 08:04:20 0000 ------- 
Ok, this should be fine now ...