The build of xmms2 fails because of HASH(0x82db558)="" in the environment
Bug #87077 reported by
Michael Bienia
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SCons |
Fix Released
|
Low
|
|||
launchpad-buildd |
Fix Released
|
Undecided
|
Adam Conrad | ||
scons (Ubuntu) |
Fix Released
|
Undecided
|
Michael Bienia |
Bug Description
The build of xmms2 fails with
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `env - DEB_BUILD_
The full build log is at http://
The package builds cleanly in a pbuilder and on Debian's buildds but not on Ubuntu's ones.
I tried to get help in #ubuntu-devel and someone said it looks like a perl hash and it might be a bug in sbuild.
I was redirected to Adam Conrad but he seems to be busy with other things.
Changed in scons: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in scons: | |
status: | New → Confirmed |
Changed in scons: | |
status: | Unknown → Confirmed |
Changed in launchpad-buildd: | |
assignee: | nobody → adconrad |
Changed in scons: | |
status: | Confirmed → Fix Released |
Changed in scons: | |
importance: | Unknown → Low |
To post a comment you must log in.
On Wed, May 16, 2007 at 05:14:10PM +0200, Michael Bienia wrote: /bugs.launchpad .net/launchpad- buildd/ +bug/87077
> 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:/
>
> 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:
http:// librarian. launchpad. net/7540965/ buildlog_ ubuntu- gutsy-i386. xmms2_0. 2DrHouse- 3.1ubuntu3_ FAILEDTOBUILD. txt.gz
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.