Quoting Jed Brown (2013-04-09 16:57:05)
> Justus Winter <4winter at 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_LIBRA
Hi Jed,
Quoting Jed Brown (2013-04-09 04:47:26)
> If libnotmuch.so is installed to a path that is not searched by
> dlopen(3), we must import it using an absolute path because the Python
> bindings do not have the luxury of RPATH linking. So strip off the
> trailing directories from the install l
On Tue, Apr 09 2013, David Bremner wrote:
> Tomi Ollila writes:
>
>> On Tue, Apr 09 2013, Jed Brown wrote:
>>
>>> David Bremner writes:
>>>
Squashed sounds good to me too. Sorry I'm too lazy/busy at the moment to
do it myself.
>>>
>>> I tested the attached and it's working as expected.
ubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20130409/2492320e/attachment.pgp>
Justus Winter <4winter at informatik.uni-hamburg.de> writes:
> 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
RPAT
Justus Winter <4winter at 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 confi
On Tue, Apr 09 2013, Jed Brown wrote:
> David Bremner writes:
>
>> Squashed sounds good to me too. Sorry I'm too lazy/busy at the moment to
>> do it myself.
>
> I tested the attached and it's working as expected. Sent as an
> attachment to preserve author information.
LGTM (this time tested, to
Tomi Ollila writes:
> On Tue, Apr 09 2013, Jed Brown wrote:
>
>> David Bremner writes:
>>
>>> Squashed sounds good to me too. Sorry I'm too lazy/busy at the moment to
>>> do it myself.
>>
>> I tested the attached and it's working as expected. Sent as an
>> attachment to preserve author informat
Justus Winter <4win...@informatik.uni-hamburg.de> writes:
> 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
RPATH i
Quoting Jed Brown (2013-04-09 16:57:05)
> Justus Winter <4win...@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_
Justus Winter <4win...@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 configur
Hi Jed,
Quoting Jed Brown (2013-04-09 04:47:26)
> If libnotmuch.so is installed to a path that is not searched by
> dlopen(3), we must import it using an absolute path because the Python
> bindings do not have the luxury of RPATH linking. So strip off the
> trailing directories from the install l
On Tue, Apr 09 2013, David Bremner wrote:
> Tomi Ollila writes:
>
>> On Tue, Apr 09 2013, Jed Brown wrote:
>>
>>> David Bremner writes:
>>>
Squashed sounds good to me too. Sorry I'm too lazy/busy at the moment to
do it myself.
>>>
>>> I tested the attached and it's working as expected.
Tomi Ollila writes:
> On Tue, Apr 09 2013, Jed Brown wrote:
>
>> David Bremner writes:
>>
>>> Squashed sounds good to me too. Sorry I'm too lazy/busy at the moment to
>>> do it myself.
>>
>> I tested the attached and it's working as expected. Sent as an
>> attachment to preserve author informat
On Mon, Apr 08, 2013 at 06:56:26PM -0300, David Bremner wrote:
> Sure, no blame attaches. But somebody still needs to fix the patch or
> convince us it doesn't need fixing.
According to git grep -C2 _notmuch_message_gen_terms, there are
seven calls to this function. Returned status checked zero
15 matches
Mail list logo