You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Clang/LLVM 19.1.2, and encountered an error in a cross build of Chromium (host = Linux on AMD64, target = Windows on ARM64), along these lines:
This error occurred due to the presence of a videodsp.asm file in the assembler's working directory. This file had been generated in a previous build step, and it contained preprocessed assembler source for aarch64. The assembler picked it up for some reason and attempted to generate AMD64 code from it.
Further investigation showed where the videodsp.asm file came from: an invocation of clang-cl. But it was not the Chromium build's intended invocation, which is as follows:
Note how the first command writes the preprocessed source to a temporary file (-o /tmp/videodsp-bb587f.asm), whereas the second just writes it to a path-less file (-o videodsp.asm).
As the Chromium build error I presented above illustrates, writing unexpected intermediate files to the current directory should be avoided.
The text was updated successfully, but these errors were encountered:
I am using Clang/LLVM 19.1.2, and encountered an error in a cross build of Chromium (host = Linux on AMD64, target = Windows on ARM64), along these lines:
This error occurred due to the presence of a
videodsp.asm
file in the assembler's working directory. This file had been generated in a previous build step, and it contained preprocessed assembler source for aarch64. The assembler picked it up for some reason and attempted to generate AMD64 code from it.Further investigation showed where the
videodsp.asm
file came from: an invocation ofclang-cl
. But it was not the Chromium build's intended invocation, which is as follows:That works as expected, with an
.obj
file written out, and no other side effects.However, when
ccache
is in use, the command is modified slightly into the following:And for reasons unknown, this invocation generates a
videodsp.asm
file in the current working directory.Here is the full output from an invocation of the first command above, with
-v
added:And here is the same for the second command:
Note how the first command writes the preprocessed source to a temporary file (
-o /tmp/videodsp-bb587f.asm
), whereas the second just writes it to a path-less file (-o videodsp.asm
).As the Chromium build error I presented above illustrates, writing unexpected intermediate files to the current directory should be avoided.
The text was updated successfully, but these errors were encountered: