Replies: 5 comments
-
|
@arrowd, What you are attempting is not supported. There is not a supported path where you can build 10 from previously source-built 9.0 assets. The .NET team allows the use of the in-development features before they are released during previews. This requires distro maintainers to have to re-bootstrap on every major release. |
Beta Was this translation helpful? Give feedback.
-
|
How do I proceed, then? How were the first v10 Linux prebuilts produced anyways? |
Beta Was this translation helpful? Give feedback.
-
You would have to bootstrap with the Microsoft SDK and artifacts. |
Beta Was this translation helpful? Give feedback.
-
|
There are no SDKs for FreeBSD produced by Microsoft. How are these SDKs produced? |
Beta Was this translation helpful? Give feedback.
-
Would likely have to build your own since it is community supported or utilize others mentioned in #1139 (comment) and dotnet/runtime#102377 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the Bug
I'm building dotnet/dotnet@ceda881 using .NET 9.0.10 (see below why I'm doing this). The process successfully produces the
Private.SourceBuilt.Artifacts.10.0.100-alpha.1.24530.1archive. Then I use these10.0.100-alpha.1.24530.1artifacts and SDK to build the latest 10.0 RC, but it quickly fails with errors likeFrom what I read in
NU1103error's description, this happens because-alphaversions are not considered during the dependency resolution. However, unpacking some.nupkgs fromPrivate.SourceBuilt.Artifacts.10.0.100-alpha.1.24530.1reveals, that dependencies listed in their.nuspecs have9.0.9for some reason:Why I'm doing this
The platform I'm compiling on is FreeBSD. We do not have a luxury of using prebuilt .NET binaries that are usually used for bootstrapping the VMR build. Since it isn't possible to build the latest .NET 10 RC using the latest .NET 9, I tried to perform the bootstrapping in multiple steps. The
ceda881686f48350dc079304ff15edcbeda6c5e3can be built with .NET 9, but using it for further builds results in a problem described above.Beta Was this translation helpful? Give feedback.
All reactions