Re: [Bugme-new] [Bug 15111] New: rpath $ORIGIN useless when path contains colon

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Sat, 23 Jan 2010 02:11:37 GMT bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
>> I am trying to embed Python into the Source (Half-Life 2) game engine. Many
>> game server providers place servers in paths containing colons (e.g.,
>> /home/srcds/93.76.8.1:27015/). Because of the way my program is called in (it
>> is a shared library), the search path does not include the directory my shared
>> library is in. Thus, I must use an RPATH and the RPATH variable $ORIGIN, which
>> expands to the directory my shared library is in.
>>
>> Unfortunately, when $ORIGIN is expanded, it contains a colon, and the runtime
>> linker treats it as two individual paths, searching in "/home/srcds/93.76.8.1"
>> and "27015/". The game server providers do not allow access to the directory
>> where the server is run, so it is inconvenient to place the python25.so there.

That's an issue of the runtime linker (ld.so, part of glibc), it has
nothing to do with the kernel. Or am I missing something?


Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux&nblp;USB Development]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite Secrets]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux