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
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
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
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
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
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 configure: we
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_PATH.
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 is bad
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 location and try CDLL with an
absolute path.
---
This is
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 location and try CDLL with an
absolute path.
---
This is
10 matches
Mail list logo
