-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workaround for build failure in cdacreader
when EmitCompilerGeneratedFiles=true
#101279
Workaround for build failure in cdacreader
when EmitCompilerGeneratedFiles=true
#101279
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
This comment was marked as spam.
This comment was marked as spam.
After this PR, there is an error during coreclr camke-config step by command #### linux-debian-AMD64 and loongarch64 are both failed !!!
./build-runtime.sh -debug -loongarch64 -nopgooptimize -skipmanaged
-- Looking for process_vm_readv
-- Looking for process_vm_readv - found
CMake Error at debug/runtimeinfo/CMakeLists.txt:57 (message):
No cdac-build-tool set or does not exist
-- Configuring incomplete, errors occurred!
See also "/home/qiao/work_qiao/runtime/artifacts/obj/coreclr/linux.loongarch64.Debug/CMakeFiles/CMakeOutput.log".
See also "/home/qiao/work_qiao/runtime/artifacts/obj/coreclr/linux.loongarch64.Debug/CMakeFiles/CMakeError.log". #100650 |
@shushanhf This PR is fixing a different problem (from before #100650 went in) and is unrelated to that error. @lambdageek's change in #101297 should be addressing that one. |
…tnet#101279) When we build `cdacreader`, we run the `LinkNative` target. This depends on `Compile` not `Build`, which means the `BuildOnlySettings` target that sets `BuildingProject=true` doesn't run. When `EmitCompilerGeneratedFiles=true`, this results in the generated output path not being created and the compiler erroring when trying to emit files to the path. See dotnet/roslyn#73075. CodeQL injects `-p:EmitCompilerGeneratedFiles=true` into the command line arguments. This was resulting in build failures in jobs where CodeQL is run. This change adds a workaround to our infrastructure for building NativeAOT-ed runtime components such that the generated output path is always created if `EmitCompilerGeneratedFiles=true`. Manually tested by explicitly passing that property on the command line. Fixes dotnet/source-build#4335
When we build
cdacreader
, we run theLinkNative
target. This depends onCompile
notBuild
, which means theBuildOnlySettings
target that setsBuildingProject=true
doesn't run. WhenEmitCompilerGeneratedFiles=true
, this results in the generated output path not being created and the compiler erroring when trying to emit files to the path. See dotnet/roslyn#73075.CodeQL injects
-p:EmitCompilerGeneratedFiles=true
into the command line arguments. This was resulting in build failures in jobs where CodeQL is run.This change adds a workaround to our infrastructure for building NativeAOT-ed runtime components such that the generated output path is always created if
EmitCompilerGeneratedFiles=true
. Manually tested by explicitly passing that property on the command line.Fixes dotnet/source-build#4335