fsprojects / fsprojects/Paket

`dotnet paket restore` fails on M1

Open
#4,146 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

I'm trying to open Fantomas solution on a Mac with M1 processor, but restore fails like this:

eugene@Eugenes-Air:fantomas$ dotnet paket restore
Failed to load /usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.5/libhostpolicy.dylib, error:
  dlopen(/usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.5/libhostpolicy.dylib, 0x0001):
    tried: '/usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.5/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e'))
An error occurred while loading required library libhostpolicy.dylib from [/usr/local/share/dotnet/shared/Microsoft.NETCore.App/5.0.5]

Fantomas uses Paket 7.0.2 and I've tried updating it to 7.1.5 locally.
.NET info:

eugene@Eugenes-Air:fantomas$ dotnet --version
6.0.202

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing dotnet paket restore on an M1 Mac and inspect the reported .NET runtime architecture mismatch, using the .NET info output in the issue as the baseline. Done means Paket restore completes successfully on the reported ARM environment, with the cause or required compatibility change identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp, macos
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.