From: Michal Marek <mmarek@suse.cz>
To: they4kman@gmail.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 15111] New: rpath $ORIGIN useless when path contains colon
Date: Sat, 23 Jan 2010 13:59:21 +0100 [thread overview]
Message-ID: <4B5AF2A9.3020103@suse.cz> (raw)
In-Reply-To: <20100122182653.7b657b3a.akpm@linux-foundation.org>
> On Sat, 23 Jan 2010 02:11:37 GMT bugzilla-daemon@bugzilla.kernel.org 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
prev parent reply other threads:[~2010-01-23 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15111-10286@http.bugzilla.kernel.org/>
2010-01-23 2:26 ` [Bugme-new] [Bug 15111] New: rpath $ORIGIN useless when path contains colon Andrew Morton
2010-01-23 12:59 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B5AF2A9.3020103@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=they4kman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).