On Fri, Aug 12, 2005 at 09:49:50PM +0200, Marc 'HE' Brockschmidt wrote: > Package: djview > Severity: serious
> I just looked through the whole mess with djvulibre and noticed that > it was only built on two official archs (i386, uploaded by the > maintainer, and sparc). m68k fails due to a toolchain bug, hppa due to > the broken fakeroot on the buildds and the other fail because they can't > link in Xinerama - I have no idea why this was successful on the sparc > buildd. It succeeded on sparc because sparc was the last architecture to get xorg-x11 built, so djvulibre built there against the old -dev packages that didn't yet have libxinerama-dev split out. (That's fixd now anyway in the latest xorg-x11 upload, so is ignorable.) arm seems to fail for a completely different reason, btw. > Anyway, the sparc binaries are broken, as announced in the build log: > /usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/libqt-mt.so, may > conflict with libstdc++.so.6 > This means that the current version of djview is broken on sparc (and > probably on i386, iff the maintainer used an up-to-date system to > build). In spite of this rather specific ld warning, *if* ld succeeds in linking an application against two versions of libstdc++, this is much less likely to cause breakage than linking in two versions of almost any other library, because libstdc++ uses fully versioned symbols. So that alone doesn't seem to warrant an RC bug, unless you have some empirical evidence that the program is broken. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
