Open Bug 1514671 Opened 6 years ago Updated 2 years ago

AS gets set to ccache when ccache is used

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Version:
64 Branch
Type:
defect

Tracking

(firefox64 fix-optional)

Tracking Flags:
Tracking Status
firefox64 --- fix-optional

People

(Reporter: bjorn.bidar, Unassigned)

References

Details

(Keywords: in-triage, regression, regressionwindow-wanted)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce: Build Firefox with CC="ccache gcc" Actual results: AS = /usr/bin/ccache (in autoconf.mk) compile error during running AS: /usr/bin/ccache -o xptcinvoke_asm_x86_64_unix.i_o -DNDEBUG=1 -DTRIMMED=1 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_ INTERNAL_API -DIMPL_LIBXUL -fPIC -Wa,--noexecstack -include /home/bidar/dev/arch/aur/firefox-kde-opensuse/src/mozilla-unified/obj-x86_64- pc-linux-gnu/mozilla-config.h -DMOZILLA_CLIENT -g -I/home/bidar/dev/arch/aur/firefox-kde-opensuse/src/mozilla-unified/xpcom/reflect/xptca ll -c /home/bidar/dev/arch/aur/firefox-kde-opensuse/src/mozilla-unified/xpcom/reflect/xptcall/md/unix/xptcinvoke_asm_x86_64_unix.S 0:31.13 ccache: error: missing equal sign in "xptcinvoke_asm_x86_64_unix.i_o" Expected results: AS = $(CC) (worked in Firefox 63)
status-firefox64: --- → affected
Component: Untriaged → General
Keywords: regression, regressionwindow-wanted
Product: Firefox → Firefox Build System
Keywords: in-triage
This is almost certainly a regression from bug 1397263.
Blocks: 1397263
I don't think we'd spin a 64 dot release for this (so: fix-optional) but of course a fix is welcome.
status-firefox64: affected → fix-optional
I'm not familiar with the mozilla build system. However what about adding an exception for ccache or shouldn't it count as provided_assembler.wrapper?

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.