245060 - creating example config fails

Status: VERIFIED INVALID

(Webtools Graveyard :: Tinderbox, defect)

Description

[Christian :Biesinger (don't email me, ping me on IRC)]

$ perl ./build-seamonkey.pl --example-config > tinder-config.pl
Bizarre copy of ARRAY in leavesub at build-seamonkey-util.pl line 1332.
BEGIN failed--compilation aborted at build-seamonkey-util.pl line 1332.
Compilation failed in require at ./build-seamonkey.pl line 7.

this is:
$ perl --version
 
This is perl, v5.8.4 built for i386-linux-thread-multi
 
[...]

Comment 1

[Chris McAfee]

This worksforme on perl 5.8.3 on fedora/fc2.

The line number you're referencing is pointing at a signal-related
function, it's possible we're hitting some OS/version problem here.
What OS are you on?  Did this work for you before, or can you
try another OS so we could narrow this down?

Comment 2

[Stephen Walker]

This seems to be caused by a perl 5.8.4 bug.

http://www.perldiscuss.com/article.php?id=10276&group=perl.perl5.changes
http://www.perldiscuss.com/article.php?id=10531&group=perl.perl5.changes

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #1)
> This worksforme on perl 5.8.3 on fedora/fc2.
> 
> The line number you're referencing is pointing at a signal-related
> function, it's possible we're hitting some OS/version problem here.

oh great...

> What OS are you on?  Did this work for you before, or can you
> try another OS so we could narrow this down?

This was on linux (debian unstable); happened on two such machines.
And it's not only creating example config, but also running the tinderbox that's
broken (swalker thankfully sent me a default tinder-config.pl)

this is the first time I'm setting up a tinderbox.

(In reply to comment #2)
> This seems to be caused by a perl 5.8.4 bug.

*sigh*
so I need to wait for a new perl version?

Comment 4

[Chris McAfee]

You could pull down perl 5.8.3 and put it next to the
default perl you have now, say /usr/local/perl-5.8.3, and
then use this perl to get around 5.8.4 bugs if that really
is the problem.  You would need to hack the 1st-line headers
in the perl files to point at the new perl.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

ok, using perl 5.8.3 works...

marking invalid, as this seems to be a perl bug

Comment 6

[Chris McAfee]

verifying invalid, ok.