Closed
Bug 958234
Opened 12 years ago
Closed 12 years ago
xptcall build broken on powerpc after bug 932178
Categories
(Firefox Build System :: General, defect)
Tracking
(firefox27 unaffected, firefox28 fixed, firefox29 fixed)
RESOLVED
FIXED
mozilla29
| Tracking | Status | |
|---|---|---|
| firefox27 | --- | unaffected |
| firefox28 | --- | fixed |
| firefox29 | --- | fixed |
People
(Reporter: gaston, Assigned: gaston)
References
Details
Attachments
(1 file)
|
1.78 KB,
patch
|
froydnj
:
review+
|
Details | Diff | Splinter Review |
No description provided.
| Assignee | ||
Comment 1•12 years ago
|
||
When bug 932178 moved ASFILES to moz.build in xpcom/reflect/xptcall/src/md/unix, it only did the supported archs & platforms.
Build now breaks on OpenBSD/powerpc, because the xptc{invoke,stubs}_asm_ppc_openbsd.s files contain c++-like comments, which the regular gcc compiler doesnt like, since -x assembler-with-cpp is not passed anymore.
There are actually 6 .S files (the one that were migrated) and 33 .s files for 'exotic' archs & platforms. Out of those files, it seems only the ppc/openbsd files still use c++-like comments (ie //) - they were fixed to build with -x assembler-with-cpp in bug 650749, and it that same bug comments were changed from # to // (now, i dont really remember why...)
I cant speak for other oses (solaris, aix, netbsd, rhapsody (!?)) for which files were not migrated to moz.build (as i dont know if the build fails for them), but i'd like to get the trunk build clean again on openbsd/ppc before 28 migrates to beta - for that i see two possible fixes:
- move back to c-like comments, ie /* */ for the header and # for the comments at the end of line - tested working here fine.
- rename the two files to .S, which would magically fix the issue ? (to test)
opinions ?
Blocks: 932178
Hardware: x86_64 → PowerPC
Comment 2•12 years ago
|
||
(In reply to Landry Breuil (:gaston) from comment #1)
> - rename the two files to .S, which would magically fix the issue ? (to test)
This one.
| Assignee | ||
Comment 3•12 years ago
|
||
I'll let my current build with first option finish to ensure it actually runs before testing this second option, as after rereading bug 650749, it was done to fix a crash at startup... of course, i'll also prefer the renaming.
| Assignee | ||
Comment 4•12 years ago
|
||
with the comments changed, m-c built & ran fine. Now building with .s files renamed to .S (and changed accordingly in moz.build) - the build went past the asm files fine, i'll just wait for it to finish & run it tonight
| Assignee | ||
Comment 5•12 years ago
|
||
2nd option actually works, since i'm attaching the patch from it :)
Mozilla/5.0 (X11; OpenBSD macppc; rv:29.0) Gecko/20100101 Firefox/29.0
It will probably need uplift to aurora too...
Assignee: nobody → landry
Attachment #8358470 -
Flags: review?(nfroyd)
Comment 6•12 years ago
|
||
Comment on attachment 8358470 [details] [diff] [review]
Rename xptc{invoke,stubs}_asm_ppc_openbsd.s to .S
Since you're the OpenBSD guy, r+ on changing the sparc{,64} cases too, while you're at it, to maybe save yourself some time in the future.
Attachment #8358470 -
Flags: review?(nfroyd) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/8945b2a33ba9
sparc64 builds fine without touching it (i suppose because of the style of comments in it) so i'm not daring changing those :)
Building an aurora tree on ppc to check if it needs backporting..
Comment 8•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
| Assignee | ||
Updated•12 years ago
|
| Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 8358470 [details] [diff] [review]
Rename xptc{invoke,stubs}_asm_ppc_openbsd.s to .S
[Approval Request Comment]
Bug caused by (feature/regressing bug #): 932178
User impact if declined: failure to build on openbsd/powerpc
Testing completed (on m-c, etc.): WFM on m-c
Risk to taking this patch (and alternatives if risky): NPOTB
Attachment #8358470 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Attachment #8358470 -
Flags: approval-mozilla-aurora?
Comment 10•12 years ago
|
||
Backed out in https://hg.mozilla.org/releases/mozilla-aurora/rev/5ff8dfbb1bab along with the other three commits from Ryan's uplift because one of the four caused windows m5 test failures: https://tbpl.mozilla.org/php/getParsedLog.php?id=32842361&tree=Mozilla-Aurora
Comment 12•12 years ago
|
||
There's no way this was at fault for that.
https://hg.mozilla.org/releases/mozilla-aurora/rev/c417a2f38c79
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•