Sven Boemer

Yes, so far it looks like we have a path forward to fixing this for .NET 7 and 8, by cross-building for an OS with the older glibc. I'll describe...

@normj it's a fair question :) I'm aiming to get it fixed in one of the next servicing releases for .NET 7 - probably 7.0.4 (sounds like it is too...

Will do!

@normj we have a CI build of the .NET 7 runtime binaries with the fix: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_apis/build/builds/142699/artifacts?artifactName=CoreCLRProduct___Linux_arm64_release&api-version=7.0&%24format=zip. Would you be able to test using these bits? You can use the instructions...

`PublishTrimmed` is incorrect for a `netstandard2.1` library both because we don't support publishing self-contained trimmed libraries, and because trimming wasn't available until `netcoreapp3.0`. @wtgodbe Is it definitely the case that...

Setting `IsTrimmable` to `false` would prevent the library from being trimmed when consumed in apps, so it may not be what you want. I think our team needs to discuss...

No, I think it will hit the same error because some of the logic for `IsTrimmable` is imported from the KnownILLinkPack.

The same change https://github.com/dotnet/sdk/pull/29441 removes ILLink as a bundled SDK - it now needs to be downloaded based on the TFM - but it looks like aspnetcore was relying on...

> ILLink isn't in the SDK by default, but it is automatically downloaded when true is set on a project. [...] is an acceptable tradeoff for a smaller SDK size...

The use case I had was this: @LakshanF and I were developing with some locally-built analyzers, and we wanted to make sure that dotnet format was picking up the right...