From: Mark H Weaver <mhw@netris.org>
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add PCB.
Date: Wed, 11 Mar 2015 12:39:08 -0400 [thread overview]
Message-ID: <87wq2nzdxv.fsf@netris.org> (raw)
In-Reply-To: <8761a78x4l.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Wed, 11 Mar 2015 14:46:50 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> In packaging PCB I noticed that our Mesa package loads a few libraries
>>> with dlopen() but does not use absolute paths to store items. In the
>>> case of PCB, dlopen("libudev.so.0") fails and causes "pcb" die on
>>> startup with a segfault. To prevent this until the Mesa package is
>>> fixed I wrapped the executable.
>>
>> OK. Feel free to fix MESA eventually. :-)
>
> Is anyone working on this? Otherwise I'll look into it because I
> noticed mplayer2 has the same issue.
>
> Some basic help is appreciated by the way. How do we generally handle
> dlopen() uses in Guix?
>
> Does our rpath stuff not fix the issue, and why?
dlopen doesn't consult rpaths.
> When the argument is a literal string, I suppose we can patch it to be
> an absolute pathname.
Yes, when we can do this, it is usually the preferred approach.
> And when it's parameterized? E.g. when a program
> uses a private wrapper function around dlopen(), then I guess I should
> track all uses of that wrapper function?
Ideally, yes. However, it may not always be possible.
> How about when the program dlopen()s a library of its own? Should it be
> made an absolute path to the package's output directory?
Ideally, yes.
Thanks!
Mark
next prev parent reply other threads:[~2015-03-11 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 16:15 [PATCH] Add PCB Ricardo Wurmus
2015-03-10 20:34 ` Ludovic Courtès
2015-03-11 13:46 ` Taylan Ulrich Bayırlı/Kammer
2015-03-11 16:39 ` Mark H Weaver [this message]
2015-03-12 9:28 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wq2nzdxv.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).