Closed Bug 1854769 Opened 1 year ago Closed 1 year ago

build fails with disable-bootstrap in mozconfig even after successful build without disable-bootstrap

Categories

(Firefox Build System :: General, defect)

defect

Tracking

(firefox-esr115 unaffected, firefox118 unaffected, firefox119 fixed, firefox120 fixed)

RESOLVED FIXED
120 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox118 --- unaffected
firefox119 --- fixed
firefox120 --- fixed

People

(Reporter: tnikkel, Assigned: glandium)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

If I do ./mach run with "disable-bootstrap" in my .mozconfig it fails thusly

0:12.81 checking the wasm C compiler works... no
0:12.81 DEBUG: Creating /var/folders/_5/x9tcxzk90n13lf6gk0ppjpy40000gn/T/conftest.9swqxt1p.c with content:
0:12.81 DEBUG: | int
0:12.81 DEBUG: | main(void)
0:12.81 DEBUG: | {
0:12.81 DEBUG: |
0:12.81 DEBUG: | ;
0:12.81 DEBUG: | return 0;
0:12.81 DEBUG: | }
0:12.81 DEBUG: Executing: /usr/bin/clang -std=gnu99 --target=wasm32-wasi /var/folders/_5/x9tcxzk90n13lf6gk0ppjpy40000gn/T/conftest.9swqxt1p.c -c
0:12.81 DEBUG: The command returned non-zero exit status 1.
0:12.81 DEBUG: Its error output was:
0:12.81 DEBUG: | error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-wasi"'
0:12.81 DEBUG: | 1 error generated.
0:12.81 ERROR: Failed compiling a simple C source with the wasm C compiler
*** Fix above errors and then restart with "./mach build"

If I removed disable-bootstrap then the build gets past configure. If I then remove disable-bootstrap it fails again with the same error.

Blocks: mach-busted

Bisected to bug 1853271.

Note that I use disable-bootstrap so I can have a predicatable build. I happily do bootstrap if I need to, but it's annoying to have your workflow disrupted for a bootstrap download that you don't need.

Keywords: regression
Regressed by: 1853271

:glandium, since you are the author of the regressor, bug 1853271, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(mh+mozilla)

I can't reproduce. Can you attach config.log?

Flags: needinfo?(mh+mozilla) → needinfo?(tnikkel)

Sure I'll attach that in a bit. One thing I forgot to mention was that it only seems to happen on mac, at least it still seems to work on Linux.

Ok, I can reproduce on mac, and I see what's happening.

Assignee: nobody → mh+mozilla

Clearing needinfo. Let me know if you need that log or anything after all.

Flags: needinfo?(tnikkel)

Set release status flags based on info from the regressing bug 1853271

Fix by backing out bug 1853271.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in before you can comment on or make changes to this bug.