Closed
Bug 526302
Opened 15 years ago
Closed 15 years ago
Wrong OS_TEST value when cross compiling on Linux with mingw.
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.3a1
People
(Reporter: jacek, Assigned: jacek)
References
Details
Attachments
(1 file)
472 bytes,
patch
|
cls
:
review+
ted
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20091028 Gentoo Firefox/3.5.3 Build Identifier: OS_TEST is overwritten when OS_ARCH is WINNT: case "$OS_ARCH" in WINNT) OS_TEST=`uname -p` ;; It should be unchanged when cross compiling. Reproducible: Always
Assignee | ||
Comment 1•15 years ago
|
||
Assignee | ||
Updated•15 years ago
|
Attachment #409999 -
Flags: review?(cls)
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → jacek
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment on attachment 409999 [details] [diff] [review] fix The fix looks okay but incomplete. `uname -p` returns "unknown" for both cygwin & msys uname. And there are bunch of other `uname` calls in that section that should not occur when cross-compiling. rs=cls
Attachment #409999 -
Flags: superreview?(ted.mielczarek)
Attachment #409999 -
Flags: review?(cls)
Attachment #409999 -
Flags: review+
Comment 3•15 years ago
|
||
Comment on attachment 409999 [details] [diff] [review] fix Yeah, because config.guess returns "i686-pc-mingw32" when building in MSYS, so we never hit that block, we hit this: http://mxr.mozilla.org/mozilla-central/source/configure.in#1223
Attachment #409999 -
Flags: superreview?(ted.mielczarek) → superreview+
Comment 5•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/479d37add351
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite-
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Updated•14 years ago
|
Version: unspecified → Trunk
Updated•14 years ago
|
Blocks: C192ConfSync
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•