Open Bug 1767848 Opened 2 years ago Updated 2 years ago

`mach hazards build-shell` fails to find gcc, with a broken path string

Categories

(Firefox Build System :: General, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: saschanaz, Assigned: sfink)

References

(Blocks 1 open bug)

Details

> ./mach hazards build-shell
created virtual environment CPython3.10.4.final.0-64 in 32ms
  creator CPython3Windows(dest=C:\Users\sasch\Documents\GitHub\gecko-dev\obj-haz-shell\_virtualenvs\build, clear=False, no_vcs_ignore=False, global=False)
  activators BashActivator,BatchActivator,FishActivator,PowerShellActivator,PythonActivator
 0:02.05 Clobber not needed.
 Config object not found by mach.
 0:02.50 Using Python 3.10.4 from C:\users\sasch\documents\github\gecko-dev\obj-haz-shell\_virtualenvs\build\Scripts\python.exe
 0:02.50 Adding configure options from C:\users\sasch\documents\github\gecko-dev\js\src\devtools\rootAnalysis\mozconfig.haz_shell
 0:02.50   --enable-ctypes
 0:02.50   --enable-optimize
 0:02.50   --disable-debug
 0:02.51   --enable-application=js
 0:02.51   --enable-nspr-build
 0:02.51 checking for vcs source checkout... git
 0:02.58 checking for a shell... C:/mozilla-build/msys2/usr/bin/sh.exe
 0:02.58 checking for host system type... x86_64-pc-mingw32
 0:02.58 checking for target system type... x86_64-pc-mingw32
 0:02.89 checking for Python 3... C:/Users/sasch/Documents/GitHub/gecko-dev/obj-haz-shell/_virtualenvs/build/Scripts/python.exe (3.10.4)
 0:02.91 checking for git... C:/PROGRA~1/Git/cmd/git.exe
 0:02.92 checking for Git version... 2.36.0.windows.1
 0:02.95 checking for sparse checkout... no
 0:02.95 checking whether cross compiling... no
 0:05.16 checking for wget... C:/mozilla-build/msys2/usr/bin/wget.exe
 0:05.19 checking for ccache... not found
 0:05.19 checking for the target C compiler... not found
 0:05.19 DEBUG: _cc: Looking for C:Userssasch/.mozbuildhazard-toolsgccbingcc
 0:05.19 ERROR: Cannot find the target C compiler
*** Fix above errors and then restart with "./mach build"

I doubt hazard builds are supported on Windows.

Flags: needinfo?(sphink)

Hm, yeah, I should figure out how to make it produce a decent error message on Windows.

./mach hazards bootstrap works, so perhaps block it first? 😛 What exactly blocks it from working btw?

Severity: -- → S4
Priority: -- → P3

(In reply to Kagami :saschanaz from comment #3)

What exactly blocks it from working btw?

The hazard analysis uses sixgill, a gcc plugin, to extract the needed information from a compile. We don't support gcc on Windows.

Flags: needinfo?(sphink)
Assignee: nobody → sphink
You need to log in before you can comment on or make changes to this bug.