Closed Bug 267416 Opened 20 years ago Closed 18 years ago

We need a high version perl to build firefox.

Categories

(Firefox Build System :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: leon.sha, Unassigned)

Details

Attachments

(2 files, 2 obsolete files)

It is OK if we build mozilla using perl version 5.0005.
But when we build firefox using this perl, the build failed.
If we use perl version 5.6.1, there will be no problem.
Attached file This is errors.
Attached patch Patch to change the configure (obsolete) — Splinter Review
Attachment #164349 - Flags: review?(bryner)
Comment on attachment 164349 [details] [diff] [review]
Patch to change the configure

-> bsmedberg, because I think he has a better idea what the current situation
is with preprocessor.pl's perl requirements
Attachment #164349 - Flags: review?(bryner) → review?(bsmedberg)
Attachment #164349 - Flags: review?(bsmedberg) → review+
Comment on attachment 164349 [details] [diff] [review]
Patch to change the configure

dbaron, any thoughts on this?  Would this require updating build machines?
Attachment #164349 - Flags: superreview?(dbaron)
Comment on attachment 164349 [details] [diff] [review]
Patch to change the configure

This might require updating otaku or something like that.  Is the issue
actually the perl version rather than a module version or something like that? 
(I guess it appears that way.)
Attachment #164349 - Flags: superreview?(dbaron) → superreview+
Attached patch Ready to check in (obsolete) — Splinter Review
Should I check in the patch now?
Checking in configure.in;
/cvsroot/mozilla/configure.in,v  <--  configure.in
new revision: 1.1407; previous revision: 1.1406
done
Checking in configure;
/cvsroot/mozilla/configure,v  <--  configure
new revision: 1.1384; previous revision: 1.1383
done
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Looks like btek needs to be updated too...
This should be backed out.  We really can't do things like that to btek (it has
a cascade of effects), so as long as we want btek to be a constant yardstick, we
can't do this.
Back out done.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #10)
> Back out done.

I ran into the same problem while attempting to build Thunderbird. The build
failed for me when it attempted to run make-jars.pl. The failure is due to the
way that getopts parses command line arguments. The Makefiles use -- to
terminate getopts argument processing but getopts in the earlier version of perl
doesn't stop there. Some of the remaining arguments look like command line
switches, getopts complains about them not being in its config string, and the
script becomes very confused. Just to make sure I checked the code for getopts
from perl versions 5.005 and 5.8.6. The code in 5.8.6 has the test for "--" and
the code for 5.005 doesn't.
Assignee: bryner → nobody
Status: REOPENED → NEW
QA Contact: asa → build.config
Surely this is no longer a bug?
Why not?  What's changed?
Attached patch v1.1Splinter Review
This is silly.  We shouldn't be holding out on fixes just because one tinderbox (of dubious value) has unique constraints that only apply to it.  If we ever start using XULPPFLAGS in SeaMonkey (maybe when SM starts using toolkit), then btek will hit this problem as well.

This patch bumps the required version to 5.6.0 and wraps the perl version check in a TINDERBOX_SKIP_PERL_VERSION_CHECK test. btek's tinderbox config needs to be updated to set that variable.
Attachment #164349 - Attachment is obsolete: true
Attachment #171975 - Attachment is obsolete: true
Attachment #227559 - Flags: review?(benjamin)
Attachment #227559 - Flags: review?(benjamin) → review+
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: