[Bug libc/10253] New: RPATH $ORIGIN breaks if resulting path has colons in it

["trick at icculus dot org" <sourceware-bugzilla at sourceware dot org>]

As the summary says, RPATH with $ORIGIN breaks if the expansion of ORIGIN 
results in a path with colons in it.  More specifically, the path is broken up 
at the colons.

For example, if an executable has RPATH set to $ORIGIN, requires a library 
(libfoo.so) that is in the same directory as the exceutable, and both files 
reside in eg /tmp/a, everything will work fine.  However, if both files reside 
in /tmp/a:b (and not in /tmp/a), the linker will be unable to find libfoo.so.  
If the executable is in /tmp/a:b but libfoo.so exists in /tmp/a, the linker 
will find /tmp/a/libfoo.so in stead of the one in the executable's directory.

I've tested this on Arch Linux 64-bit with glibc 2.10.1, and also on Gentoo 
Linux 32-bit with glibc 2.4.  The results are identical on both systems.

I'll attach a script that illustrates the bug.

-- 
           Summary: RPATH $ORIGIN breaks if resulting path has colons in it
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: trick at icculus dot org
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10253

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.