Bug#637236: gcc-4.6/gcj-4.6 build failures on kfreebsd-amd64 are back again
- To: Aurelien Jarno <aurelien@aurel32.net>
- Cc: Ludovic Brenta <ludovic@ludovic-brenta.org>, 637236@bugs.debian.org, debian-bsd@lists.debian.org
- Subject: Bug#637236: gcc-4.6/gcj-4.6 build failures on kfreebsd-amd64 are back again
- From: Robert Millan <rmh@debian.org>
- Date: Fri, 4 Nov 2011 23:53:47 +0100
- Message-id: <CAOfDtXMb9LXeMYbSJ_bjPaB43T7tLY2r6jG7U6TnbgM_H1=7pg@mail.gmail.com>
- Reply-to: Robert Millan <rmh@debian.org>, 637236@bugs.debian.org
- In-reply-to: <20111031113340.GK31153@hall.aurel32.net>
- References: <4EA99301.6060604@debian.org> <CAOfDtXOng1yY1zX2fkGr_cUTLL0j-NCpZnzc62u2M_wX6+iwdw@mail.gmail.com> <87sjmcg2i8.fsf@ludovic-brenta.org> <CAOfDtXPHyHFg-N3YyAs3qVp1iq_nBQ=fHHSbKTDrZrCcPmJAeA@mail.gmail.com> <877h3mf95k.fsf@ludovic-brenta.org> <20111031113340.GK31153@hall.aurel32.net>
2011/10/31 Aurelien Jarno <aurelien@aurel32.net>:
> It's worse than that, gcc-4.6 builds fine in the build daemon if the
> build is done directly in the chroot or started directly by calling
> sbuild. The problem only appears when the buildd process calls sbuild,
> which makes things difficult to debug.
Maybe something in the environment triggers it. How about adding a
call to "env" command to fill the build log with?
--
Robert Millan
Reply to: