arm64 linux build machines seem to be missing key components?

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=156337

Build leg reported

Build / CoreCLR Product Build linux arm64 checked / Build CoreCLR Runtime

Pull Request

https://github.com/dotnet/runtime/pull/81377

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

• Open the failing build above and investigate
• Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

1. Add the label “Known Build Error”
2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation

{
   "ErrorMessage" : "ld.lld: error: cannot open crt1.o: No such file or directory",
   "BuildRetry": false,
   "ErrorPattern": "",
   "ExcludeConsoleLog": false
}

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Report

Build	Definition	Step Name	Console log	Pull Request
155366	dotnet/runtime	Prepare TestHost with runtime Mono	Log	dotnet/runtime#81465
156168	dotnet/runtime	Prepare TestHost with runtime CoreCLR	Log	dotnet/runtime#78736
157049	dotnet/runtime	Build product	Log
157051	dotnet/runtime	Build product	Log
156662	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81513
156337	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81377
156713	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81517
156490	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81052
156698	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81518
156666	dotnet/runtime	Build product	Log	dotnet/runtime#81359
156653	dotnet/runtime	Build CoreCLR Runtime	Log
156632	dotnet/runtime	Build product	Log	dotnet/runtime#81439
156147	dotnet/runtime	Prepare TestHost with runtime CoreCLR	Log
156631	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81063
156421	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81510
156596	dotnet/runtime	Build product	Log
156518	dotnet/runtime	Build CoreCLR Runtime	Log
156503	dotnet/runtime	Build product	Log	dotnet/runtime#81335
156483	dotnet/runtime	Build product	Log	dotnet/runtime#81162
156435	dotnet/runtime	Build product	Log
156142	dotnet/runtime	Prepare TestHost with runtime CoreCLR	Log
156431	dotnet/runtime	Build product	Log	dotnet/runtime#81380
156413	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81509
156150	dotnet/runtime	Build	Log	dotnet/runtime#81503
156384	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81454
156194	dotnet/runtime	Build	Log	dotnet/runtime#74820
156273	dotnet/runtime	Build CoreCLR Runtime	Log	dotnet/runtime#81409
156213	dotnet/runtime	Prepare TestHost with runtime CoreCLR	Log

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	28	28

[AndyAyersMS]

Please let us know if that change addresses this issue. W

Things seem to be fixed.

As Jan says this was a problem detected by CMAKE but not a problem with CMAKE; something broke the ability to compile and link simple programs and the error was noticed by the linker. Very early in a build CMAKE will compile and run simple programs to figure out how to properly configure the build settings for the things we actually want to compile. These early compiles are a natural place to hit issues if various bits of build componentry are not present.

[jkotas]

any evidence (there) that cmake was changed.

This build break was not introduced by cmake changes. It was introduced by the arm64 cross image changes.

Given that the container updates are rolled out without any validation gates in the new system, we are going to see sudden wide-spread build breaks like this one with regular frequency.