-
Notifications
You must be signed in to change notification settings - Fork 136
Error building source-build-reference-packages using 3.1 #1946
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
Comments
This got a bit complicated due to some compatibility issues with SBRP and dotnet/source-build's source-build (source-build-reference-packages dotnet/source-build-reference-packages@f07c2d3 is in the |
Thanks. What does that mean for a Linux distribution looking to build both .NET 3.1 and 5 from source? In Fedora, we have 1 package for SBRP, and it was for 3.1. If I want to add 5.0 (and, say, start working on 6.0 builds too) what should I do? Should I build each branch of SBRP? Can I share one build of SBRP between 5.0 and 3.1? |
The branches have distinct sets of packages (and to some degree infra) so you need to build every branch into separate packages. 😕 A significant factor here is that with one branch, changes that are meant to be for Ultimately I think we should get rid of SBRP as being something special. (#1456.) I expect this to happen in 6.0 with arcade-powered source-build. |
Thanks, I was able to follow these steps and get it working locally. |
I am trying to build source-build-reference-packages commit f07c2d37ddf062561ff57a212e3513fbd0ab083a using .NET Core 3.1.
The build fails for me:
Rerunning the failing command manually shows this error:
Is this a known issue? Is it supported to use .NET Core 3.1 to build recent commits of source-build-reference-packages?
The text was updated successfully, but these errors were encountered: