[email protected]
[Top] [All Lists]

Re: Tracking down scons FTBFS issues.

Subject: Re: Tracking down scons FTBFS issues.
From: Matt Zimmerman
Date: Wed, 16 May 2007 16:40:41 +0100
On Wed, May 16, 2007 at 05:14:10PM +0200, Michael Bienia wrote:
> On 2007-05-16 12:55:43 +0100, Matt Zimmerman wrote:
> > If that's what it is, you'll probably need to look at config.log to find out
> > what's wrong; one way to debug this type of failure is to do something
> > analogous to:
> > 
> > ./configure ... || (cat config.log; false)
> I've done it for xmms2 already which uses also scons to build and fails
> only on the Ubuntu buildds (but builds fine in a pbuilder and in
> Debian).
> The result was that the environment had a HASH(0x82db558)="" (the hex
> value differs between builds) which /bin/sh didn't like and errors out
> which scons interprets as not found.
> After consulting #ubuntu-devel I got told that this it probably a bug in
> the sbuild on the buildds and that I should ask Adam Conrad about it.
> I contacted him and told him about this problem and wait now till he
> finds some time to look at it and fix it.
> I've also already opened a bug about it:
> https://bugs.launchpad.net/launchpad-buildd/+bug/87077
> I assume that other packages using scons trigger this bug also and that
> at least aqsis and a package I already forgot have probably the same
> problem (I didn't upload a new version to get the config.log to confirm
> it).

The build log URL in that bug report isn't valid, and the one I could find:


doesn't show that line.  I'd like to see the full build log.

That environment value looks like a bug in a Perl program.  It shouldn't
break sbuild, but it shouldn't be there either.

 - mdz

ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: 

<Prev in Thread] Current Thread [Next in Thread>