While trying to build the latest GIT / Alpha18 of Samba 4 in a
"distribution-friendly" way on Gentoo, I ran into some problems
regarding the rpath entries of the Python C extensions included with
More precisely, I specified (among others) the following configure options
which places all the Samba modules in /usr/lib/samba.
Nonetheless, the rpath entry of several Python modules only
contains /usr/lib, instead of /usr/lib:/usr/lib/samba.
A recent conversation on the samba-technical mailing list revealed that this seems to be due to a bug in wafsamba.
For the time being, I was able to circumvent the issue by making some of the Python modules' implicit dependencies explicit ones in the respective wscript_build scripts.
Nonetheless, a more permanent fix to the problem would be much appreciated.
Jelmer, could you have a look, please?
(In reply to comment #1)
> Jelmer, could you have a look, please?
See the conversation on the mailing list. I don't have time to look into this at the moment.
(In reply to comment #0)
> More precisely, I specified (among others) the following configure options
> which places all the Samba modules in /usr/lib/samba.
What's the exact configure command did you use?
I used the following command:
configure --prefix=$HOME/samba/prefix1 \
I can see all the modules are installed under $HOME/samba/prefix1/lib64 and
not samba subdir ($HOME/samba/prefix1/lib64/samba).
Also the rpath entries exist only for private libs.
First of all, I forgot to mention that the problem only occurs while compiling with system talloc, tevent, tdb, and ldb. But that's something you definitely want while packaging for a distribution.
(In reply to comment #3)
> What's the exact configure command did you use?
On my system (amd64), the Gentoo waf eclass constructs the following line to configure the source:
CCFLAGS="-O3 -march=native -pipe" \
LINKFLAGS="-Wl,-O1 -Wl,--as-needed" \
--disable-rpath --disable-rpath-install \
Amitay, can you try building with in-system talloc, tevent, tdb, and ldb, and see, if you can reproduce the problem then?
did you meanwhile have a chance to try the aforementioned setup?
The problem seems to be fixed in Beta3.