Package: xorg-x11 Version: 6.8.2.dfsg.1-7 Tags: FTBFS Building xorg-x11 from source fails (i386, gcc 4.0):
[...] dh_fixperms chown root:root debian/xserver-common/usr/X11R6/bin/X chmod ug+s debian/xserver-common/usr/X11R6/bin/X chown :utmp debian/xterm/usr/X11R6/bin/xterm chmod g+s debian/xterm/usr/X11R6/bin/xterm dh_installdeb dh_shlibdeps -Nlibdps1 -Nlibx11-6 -l/opt/debian/build/xorg-x11-6.8.2.dfsg.1/debian/tmp/usr/lib -l/opt/debian/build/xorg-x11-6.8.2.dfsg.1/debian/tmp/usr/X11R6/lib --exclude=usr/X11R6/lib/modules Use of uninitialized value in scalar assignment at /usr/bin/dh_shlibdeps line 138, <COMPAT_IN> line 2. [...] Use of uninitialized value in scalar assignment at /usr/bin/dh_shlibdeps line 138, <COMPAT_IN> line 262. dpkg-shlibdeps: failure: ldd on `debian/xterm/usr/X11R6/bin/xterm' gave error exit status 1 dh_shlibdeps: command returned error code 256 make: *** [stampdir/binary-arch] Error 1 Build command 'cd xorg-x11-6.8.2.dfsg.1 && dpkg-buildpackage -b -uc' failed. E: Child process failed Fetched 52.0MB in 9s (5337kB/s) Problem was: amd64-libs was installed, which diverted /usr/bin/ldd. This diverted ldd however worked for all other binaries I tested, except this xterm binary. After uninstalling the package "amd64-libs", "ldd" works as expected. That looks like a bug in amd64-libs; to work around this, you may decide to build-conflict against it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
