fails to detect architectures where -latomic is needed
Categories
(Firefox Build System :: General, defect)
Tracking
(firefox-esr115 unaffected, firefox-esr128 fixed, firefox130 wontfix, firefox131 fixed, firefox132 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | fixed |
| firefox130 | --- | wontfix |
| firefox131 | --- | fixed |
| firefox132 | --- | fixed |
People
(Reporter: smcv, Assigned: sergesanspaille)
References
(Regression)
Details
(Keywords: regression)
Attachments
(4 files, 1 obsolete file)
|
1.32 KB,
patch
|
Details | Diff | Splinter Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr128+
|
Details | Review |
Steps to reproduce:
Build SpiderMonkey JavaScript library (mozjs128, as used by gjs) on Debian armel (armv5te little-endian EABI softfloat).
Actual results:
"checking whether 64-bits std::atomic requires -latomic... do not know; assuming no"
(This happens when linking a 64-bit atomic operation without -latomic fails, but linking the same code with -latomic also fails. Perhaps this should be a fatal error?)
Expected results:
The build system should be able to detect that -latomic is required.
| Reporter | ||
Comment 1•1 year ago
|
||
This seems to be a bug in the detection code. When it tries to link with arguments that end with ["-latomic"], a single string is passed where a sequence of strings is expected, so what actually happens is that it tries to link with arguments that end with ["-", "l", "a", "t", "o", "m", "i", "c"] which is not going to work.
| Reporter | ||
Comment 2•1 year ago
|
||
proposed patch (I haven't verified that the whole build finishes successfully, but it does successfully detect that -latomic is required)
| Reporter | ||
Comment 3•1 year ago
|
||
The build does succeed with the patch above. There are test failures, but they seem to be unrelated.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
:sergesanspaille, since you are the author of the regressor, bug 1883940, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 5•1 year ago
|
||
Original patch by Simon McVittie <smcv@debian.org>
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1883940
| Assignee | ||
Updated•1 year ago
|
Comment 9•1 year ago
|
||
The patch landed in nightly and beta is affected.
:sergesanspaille, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox131towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 10•1 year ago
|
||
Original patch by Simon McVittie <smcv@debian.org>
Original Revision: https://phabricator.services.mozilla.com/D220988
Updated•1 year ago
|
Comment 11•1 year ago
|
||
beta Uplift Approval Request
- User impact if declined: Architecture requiring libatomic won't compile
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: run
./mach buildand make sur it builds. If it fails on libatomic then we have an issue. - Risk associated with taking this patch: None
- Explanation of risk level: tested on nightly and by the original bug reporter
- String changes made/needed: No
- Is Android affected?: no
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 12•1 year ago
|
||
| uplift | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 14•1 year ago
|
||
Original patch by Simon McVittie <smcv@debian.org>
Original Revision: https://phabricator.services.mozilla.com/D220988
| Assignee | ||
Comment 15•1 year ago
|
||
Original patch by Simon McVittie <smcv@debian.org>
Original Revision: https://phabricator.services.mozilla.com/D220988
Updated•1 year ago
|
Updated•1 year ago
|
Comment 16•1 year ago
|
||
esr128 Uplift Approval Request
- User impact if declined: Cannot build on some architecture (eg. armel)
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: Build SpiderMonkey JavaScript library (mozjs128, as used by gjs) on Debian armel (armv5te little-endian EABI softfloat).
- Risk associated with taking this patch: none
- Explanation of risk level: tested on bookmarks/central
- String changes made/needed: no
- Is Android affected?: no
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 17•1 year ago
|
||
| uplift | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Description
•