Hey, folks.  As of today I am for some reason no longer able to build
the Notmuch Debian package.  I'm using the same build technique I have
been using for a while (git-buildpackage).  The tail of the failing
build log is pasted at the bottom of this message.  Is anyone else
encountering anything like this?

I don't see what of the recent packaging changes, other than the RPATH
stuff, could be affecting this, and I get the same failure even if I
revert the revert of the RPATH override (ie. RPATH_LDFLAGS auto-build
override in place).  I did recently do a system upgrade, so it's
possible that something there could have caused the problem.

What could be preventing dpkg-shlibdeps from finding libpthread.so.0 or
libc.so.6?

jamie.


servo:~/src/notmuch/git [master] 1$ git buildpackage -us -uc --git-ignore-branch
...
dpkg-shlibdeps: error: couldn't find library libpthread.so.0 needed by 
debian/notmuch/usr/bin/notmuch (ELF format: 'elf64-x86-64'; RPATH: '').
dpkg-shlibdeps: error: couldn't find library libc.so.6 needed by 
debian/notmuch/usr/bin/notmuch (ELF format: 'elf64-x86-64'; RPATH: '').
dpkg-shlibdeps: error: Cannot continue due to the errors listed above.
Note: libraries are not searched in other binary packages that do not have any 
shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set 
LD_LIBRARY_PATH.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/notmuch.substvars 
debian/notmuch/usr/bin/notmuch returned exit code 2
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
debuild: fatal error at line 1340:
dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed
gbp:error: debuild -i -I returned 29
gbp:error: Couldn't run 'debuild -i -I -us -uc'
servo:~/src/notmuch/git [master] 1$ 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 
<http://notmuchmail.org/pipermail/notmuch/attachments/20110624/8ca4b80a/attachment-0001.pgp>

Reply via email to