On 10/10/2012 09:30 PM, Bertrand Marc wrote: > Dear Christian, > > Thank you for checking all these Debian bugs, it is really appreciated. > > Yes my patch would place the NSS library in /usr/lib, I thought it was > ok. And my Debian scripting expect it in /usr/lib because that is where > it ends up on my amd64 box.
Now _that_ is strange. I had specifically modified our Makefiles so that it would not end up in /usr/lib. Now, I don't recall in which version I fixed that and I also don't know which one you tested on your box, but SVN HEAD AFAIK goes to /lib (if it can). > It also built fine on a lot of Debian arch > since 0.9 with this scripting. Build OK or also installed to /lib as-it-should? > In fact I don't understand how the NSS > library could end up in 2 different locations with the same GNUnet > version and the same packaging. That I also don't know. > I'll fix my package so the packaging will expect the NSS library in > /lib. But how could I be sure that the NSS library will end up there ? I think the answer is here: if HAVE_SUDO nssdir = /lib/ else nssdir = $(libdir) endif So the /lib/ installation happens if "HAVE_SUDO" is set. That was done because if a normal user runs 'make install' (say with prefix of $HOME), then we cannot install the nss lib to /lib/. Note that the test for 'HAVE_SUDO' in configure includes the ability to write to '/' as an alternative: AM_CONDITIONAL([HAVE_SUDO], [test "x$SUDO_BINARY" != "x" -o -w /]) So either run configure as 'root' or give it --with-sudo. I hope this helps! Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
