hrm hrm! bbconf can't build on sparc and s390, but why?
Take a look at these:
http://buildd.debian.org/fetch.php?&pkg=bbconf&ver=1.10-4&arch=s390&stamp=1093500225&file=log&as=raw
http://buildd.debian.org/fetch.php?&pkg=bbconf&ver=1.10-4&arch=i386&stamp=1093498536&file=log&as=raw
The configure fails because it can't find the X libraries. It *can*
find the X headers, incidentally, because it checks that first and
would bail with a "can't find X headers" error first.
The configure script is looking for things that are in libx11-6.
Now if you look at the failing s390 log (the sparc one too) and the
winning i386 log, you'll see that the s390 buildd is not installing
libx11-6, and the i386 buildd is.
But the s390 build *is* getting the correct libx11-dev binary package,
which does in fact depend on libx11-6 (I checked!). So something,
somewhere, on the s390 buildd systems is providing libx11-6 but not
actually putting the libraries in place. Else, why would the apt-get
inside the buildd run not actually install libx11-6?
On the sparc build, things are even worse. While xlibs-dev is getting
installed, the dependency libx11-dev is not getting installed at all.
Well, grr!
(Indeed, notice that xfree86-common gets installed on the winning i386
build, and not on the failing s390 build.)
Also, the failing s390 build installs the curious package
"xlibs-devxlibs-static-dev". What's that? packages.debian.org
doesn't seem to know about it.
Something very curious is up. What??
Thomas
Reply to: