On 28/05/08 at 15:22 +0200, Florian Weimer wrote: > * Lucas Nussbaum: > > >> I don't see such a failure with GCC 4.3. What did you do to set up the > >> build chroot? > > > > I didn't say that this bug was caused by gcc 4.3. It's just a > > possibility. > > > > The chroot is a minimal build chroot (debootstrap ; apt-get install > > build-essential ; debfoster to remove all the non-essential stuff) > > Yes, but how did you switch to GCC 4.3?
hacked gcc-defaults package. You can just override the gcc/g++ symlinks. > Do you use Selinux? Yes > Does the > kernel support Unix domain sockets? Yes. The kernel is the etch amd64 kernel. > This version has been auto-built on i386 beofre, therefore I'm wondering > what's wrong. I don't know, but I just reproduced it on a different system. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
