From: Justus Winter <4winter@informatik.uni-hamburg.de>
To: Jed Brown <jed@59A2.org>, notmuch@notmuchmail.org
Cc: Sebastian Spaeth <Sebastian@SSpaeth.de>
Subject: Re: [RFC/PATCH] python: search parent lib directory for libnotmuch.so
Date: Tue, 09 Apr 2013 17:21:28 +0200 [thread overview]
Message-ID: <20130409152128.7736.76003@thinkbox.jade-hamburg.de> (raw)
In-Reply-To: <87obdn7nwe.fsf@mcs.anl.gov>
Quoting Jed Brown (2013-04-09 16:57:05)
> Justus Winter <4winter@informatik.uni-hamburg.de> writes:
> >
> > May I ask why you cannot use LD_LIBRARY_PATH? I too install libnotmuch
> > to a non-standard location as unprivileged user and to make this
> > library available I add its path to LD_LIBRARY_PATH.
>
> See libdir_in_ldconfig testing in configure: we make a significant
> effort to set RPATH appropriately when installing to a location that is
> not already searched (perhaps via LD_LIBRARY_PATH). This currently does
> not apply to the Python bindings, so while you can install without
> LD_LIBRARY_PATH and still run the notmuch executable fine, you must set
> LD_LIBRARY_PATH to use the Python bindings. That is the inconsistency I
> wanted to fix here.
But why do we do that? I always thought that rpath causes more
problems and is to be avoided if possible [0]. But otoh, I didn't even
knew that the notmuch build system uses rpath.
0: e.g. http://wiki.debian.org/RpathIssue
> I don't like the indirection either, but the binary is compiled with
> knowledge of prefix/RPATH, so if we wanted a single canonical location
> to specify this information, I would make it the binary.
>
> If you don't want to trust Python install directory hierarchy, we could
> have 'setup.py install' write some info about RPATH.
I actually have no strong feelings for or against this proposal. I'm
merely surprised that there is an issue that you are trying to fix
here since exactly this configuration has worked for me since the day
I started using notmuch.
And from my point of view LD_LIBRARY_PATH is the correct way to
instruct the dynamic linker (and as a similar facility the ctypes
library loader) where to look for additional libraries.
Cheers,
Justus
next prev parent reply other threads:[~2013-04-09 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 2:47 [RFC/PATCH] python: search parent lib directory for libnotmuch.so Jed Brown
2013-04-09 14:13 ` Justus Winter
2013-04-09 14:57 ` Jed Brown
2013-04-09 15:21 ` Justus Winter [this message]
2013-04-09 15:31 ` Jed Brown
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130409152128.7736.76003@thinkbox.jade-hamburg.de \
--to=4winter@informatik.uni-hamburg.de \
--cc=Sebastian@SSpaeth.de \
--cc=jed@59A2.org \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).