Your message dated Sun, 10 Jul 2011 20:47:11 +0200
with message-id <[email protected]>
and subject line Re: Bug#633406: dpkg-shlibdeps: error: couldn't find library
libc.so.6
has caused the Debian Bug report #633406,
regarding dpkg-shlibdeps: error: couldn't find library libc.so.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
633406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633406
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.16.0.3
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
For some reason I have recently been unable to build packages linked
against libc.so.6 or libpthread.so.0 because dpkg-shlibdeps keeps
failing with the following errors:
...
dh_shlibdeps
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'
This is just one example, but I have other packages that are failing
to build with the same error. This has been going on for about a
month now, after just starting at some point, presumably due to some
upgrade that I didn't pay attention too.
This may very well be a bug in libc6 or libc6-i386 (both of which are
installed on my system) since both libpthread.so.0 and libc.so.6 are
provided by those packages (although in different paths).
I really don't know what's going on here, and nor does anyone else
I've ask. Please advise. Any debugging help would be much
appreciated.
Thanks so much for the help.
jamie.
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg-dev depends on:
ii base-files 6.3 Debian base system miscellaneous f
ii binutils 2.21.52.20110606-2 The GNU assembler, linker and bina
ii bzip2 1.0.5-6 high-quality block-sorting file co
ii libdpkg-perl 1.16.0.3 Dpkg perl modules
ii make 3.81-8.1 An utility for Directing compilati
ii patch 2.6.1-2 Apply a diff file to an original
ii xz-utils 5.0.0-2 XZ-format compression utilities
Versions of packages dpkg-dev recommends:
ii build-essential 11.5 Informational list of build-essent
ii fakeroot 1.16-1 tool for simulating superuser priv
ii gcc [c-compiler] 4:4.6.0-6 GNU C compiler
ii gcc-4.4 [c-compiler] 4.4.6-6 GNU C compiler
ii gcc-4.5 [c-compiler] 4.5.3-3 The GNU C compiler
ii gcc-4.6 [c-compiler] 4.6.1-1 GNU C compiler
ii gnupg 1.4.11-3 GNU privacy guard - a free PGP rep
ii gpgv 1.4.11-3 GNU privacy guard - signature veri
ii libalgorithm-merge-perl 0.08-2 Perl module for three-way merge of
Versions of packages dpkg-dev suggests:
ii debian-keyring 2011.03.03 GnuPG keys of Debian Developers
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJOGOQZAAoJEO00zqvie6q8i7oQALmOTBV7GMnfXsXv5bvUarWv
nityzrMdghA5WJunIfgzWeKWN3Serbq8pqWBDOJSTTI9g9LPJOM2cV11q/BK7a/Q
KaBubBi5iFfgXcTjN6l5eDZjBM2E9o0LKrMI+QW5UwG+qdoE/ZzN814GWBoLgu2m
EnpNOzsS+2l9ykqTR3uL85S0RyqSKhWV8cMXpOJIygCohIwZeUy5w9oLBWdw6lLs
II31rV5/CctKAhicXbq3vnm5/li8F4sfk5J1tv0vKu+dHdbIgKSv1GnOvkughkkr
1trlB0E9P4lWtpeXQ1Q9+KkMGB6BdS2h4vu+7/iV7SbArSTYD690zovoq6D295Xh
Rwya9L8DKnDKge+UC67Z2P+QME3fOpN799lniJIM3JKbz7VJzUSUMH6tABGf299z
r0RCB1iFHJYZ0n9pbOhzC8DMrRXFwCSAjsEGcSPEUcY2ecbPa06bNx1cGFJv9eq5
VXfdSZ8zag96+G6PfjSLvgm5crPgzuNazCTRr7wYbKlgon9DHy89YRKCCPAEguT4
l7T5h14/LKeTkqG2462mjUWN9G+kac1vX92lFDAlXXh3ve8IyfS7pzUlQqBNBF4O
+x2OjZJIclPpE3GL7CcV3zK+PrhppQZ5AOBlYb85tVDY8FVCYEuG06ykx1JXCMor
VEWzV/R/fkWGhauFX3LX
=/v+u
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sun, 10 Jul 2011, Jameson Graef Rollins wrote:
> Maybe, or I'm just the first person to report it.
If all builds were failing since a month, we would have noticed it. :-)
> So that last bit looks very suspicious to me. Should I not have the
> x86_64-linux-gnu.conf file?
You definitely should. What version of libc6 do you have? Please show me the
output of "dpkg -s libc6".
$ dpkg -S /etc/ld.so.conf.d/x86_64-linux-gnu.conf
libc6: /etc/ld.so.conf.d/x86_64-linux-gnu.conf
$ sudo dpkg -Gi --force-confmiss /var/cache/apt/archives/libc6_*.deb
Something removed that file and created all your problems. It might be
libc6-i386 that did something wrong at some point. Not sure. Anyway
reinstalling that file will fix your problem, it's definitely not a bug in
dpkg.
> dpkg also doesn't seem to know where
> /etc/ld.so.conf.d/i486-linux-gnu.conf came from.
That "i486-linux-gnu.conf" is the one of libc6 on i386.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--- End Message ---
