Open Bug 1511306 Opened 7 years ago Updated 3 years ago

yasm: warning: unrecognized option `-F'

Categories

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

Product:
Firefox Build System
Component:
General
Type:
defect

Tracking

(Not tracked)

People

(Reporter: jorgk-bmo, Unassigned)

Details

I've installed the latest MozillaBuildSetup-Latest 3.2. I've done a |mach bootstrap|. I see lots of: 5:12.44 yasm: warning: unrecognized option `-F' 5:12.44 yasm: warning: can open only one input file, only the last file will be processed Unrelated: With this "upgrade" I did to solve bug 1511230, clang-cl is not crashing left, right and centre at varying locations, so I switched back to using MSVC. No idea whether this still compiles.
Sorry: clang-cl is *now* crashing left, right and centre ...
Unrelated: clang-cl dump files here: https://we.tl/t-KuzTJobRc8
Under linux, I see the same warning many times after upgrading the source tree a few hours ago. I see a similar bug report in a separate project: https://groups.google.com/forum/#!topic/android-ndk/AKo1afwyAdI I am not sure if we are unaffected as in the above NDK project at all.
I found that on my linux PC, I have yasm but not nasm (the version of nasm I had was a bit too old to compile old source tree TB/FF that I fetched in early August timeframe with the new GCC V8 [this generated pseudo ops that could not be grokked by th eold nasm, and so I removed it a few weeks ago). That may have triggered the issue: the use of nasm is substituted with yasm that does not understand additional options. Just a wild guess. In Jorg's case, maybe the Windows environment does not come with nasm in the first place.
I am building under linux. I installed nasm from the repository of my linux distribution (Debian GNU/Linux), then did configure and build. The warning disappeared. So my guess in comment 5 seems to be correct. If yasm is used instead of nasm, we see this warning. TIA
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.