-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
linux-armel checked CoreCLR_NonPortable build failing in CI #110517
Comments
Tagging subscribers to this area: @hoyosjs |
This syncs the gcc version in toolchian file with what's in the newest container build. Fixes #110517
@akoeplinger the same problem is happening on .net9-staging, do we need to create another issue? |
@akoeplinger I'm sorry for that, same problem is happening on net8-staging. |
This syncs the gcc version in toolchian file with what's in the newest container build. Fixes dotnet#110517
Thanks, opened #110792 |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=889548&view=logs&j=2eda3965-9146-55d1-4226-c3d3f8432d8f
Build error leg or test failing: Build / linux-armel checked CoreCLR_NonPortable / Build product
Pull request: #110515
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=889548
Error message validated:
[ld.lld: error: cannot open crtbeginS.o: No such file or directory
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/9/2024 6:19:26 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: