🪲 Unable to load osx-arm on GitHub runner based on macos-latest

[MariusStorhaug]

Hey,

I am building a PowerShell module called Sodium that is using Sodium.Core.1.3.5 which in turn uses libsodium.1.0.19. I'm using the osx-arm package, but when importing the module a macos-latest runner, it fails to load.

Link to the logs: https://github.com/PSModule/Sodium/actions/runs/13090567208/job/36526719781#step:5:1362

Any pointers?

[ektrah]

It seems the error message is the following:

dlopen(/Users/runner/work/Sodium/Sodium/outputs/modules/Sodium/modules/PSModule.Sodium/isolated/runtimes/osx-arm64/native/libsodium.dylib, 0x0001): tried:

'/Users/runner/work/Sodium/Sodium/outputs/modules/Sodium/modules/PSModule.Sodium/isolated/runtimes/osx-arm64/native/libsodium.dylib' (code signature invalid in <19B93499-20D6-30C1-8038-80AC26A21DE6>

'/Users/runner/work/Sodium/Sodium/outputs/modules/Sodium/modules/PSModule.Sodium/isolated/runtimes/osx-arm64/native/libsodium.dylib' (errno=85) sliceOffset=0x00000000, codeBlobOffset=0x0005DA40, codeBlobSize=0x00000C3F)

Does this still happen if you reference the 1.4.0-preview of Sodium.Core?

[MariusStorhaug]

Tried another way around, and just create a direct binding with libsodium, and get a longer list of issues, but here we go:

https://github.com/PSModule/Sodium/blob/e2ece02f42bf4ce95f1f7ce48545e15d17697ab9/src/main.ps1
Calls:
https://github.com/PSModule/Sodium/blob/e2ece02f42bf4ce95f1f7ce48545e15d17697ab9/PSModule/Sodium/Sodium.cs
Results in:
https://github.com/PSModule/Sodium/actions/runs/13165307386/job/36743952595#step:6:456

file >>path to lib<<
https://github.com/PSModule/Sodium/actions/runs/13165501014/job/36744540509#step:3:1

[ektrah]

In https://github.com/PSModule/Sodium/actions/runs/13165307386/job/36743952595#step:6:456 you can see that .NET looks for libsodium.dylib in a number of locations. Most attempts are unsuccessful ("no such file"), but there is one attempt that finds this file: /Users/runner/work/Sodium/Sodium/outputs/modules/Sodium/libs/osx-arm64/libsodium.dylib. Loading this file with the error message we've seen before, so it continues looking at the next location.

(slice 1 extends beyond end of file, fat file, but missing compatible architecture (have 'x86_64,arm64', need 'arm64e' or 'arm64')

It seems that it cannot load a fat binary (one that contains both native code for "x86_64" and "arm64" in this case). However, the exact same fat binary works just fine when running the Sodium.Core unit tests in the same GitHub Actions environment. The only difference is PowerShell...

One thing to try could be compiling libsodium.dylib for "x86_64" and "arm64" separately, instead of a fat binary. But I don't know enough about libsodium's build scripts for that. The invocation is here:

libsodium/.github/workflows/dotnet-core.yml

Line 122 in 59a98bc

run: env LIBSODIUM_FULL_BUILD=1 LIBSODIUM_SKIP_SIMULATORS=1 dist-build/apple-xcframework.sh

[ektrah]

Just to rule it out: Is the binary file used unchanged compared to the file in the NuGet package? (compare hash sums)

[MariusStorhaug]

Guessing this is it:

mkdir -p "${PREFIX}/macos/lib"
cp -a "${MACOS_X86_64_PREFIX}/include" "${PREFIX}/macos/"
for ext in a dylib; do
lipo -create
"${MACOS_ARM64_PREFIX}/lib/libsodium.${ext}"
"${MACOS_ARM64E_PREFIX}/lib/libsodium.${ext}"
"${MACOS_X86_64_PREFIX}/lib/libsodium.${ext}"
-output "${PREFIX}/macos/lib/libsodium.${ext}"
done

[MariusStorhaug]

Butchered the build process and trying slim versions.

https://github.com/MariusStorhaug/libsodium/actions/runs/13170220799/job/36759074846

[vercellone]

@MariusStorhaug libsodium is building with .Net SDK Version: 9.0.102. What version of the .Net SDK is being used to build PSModule.Sodium.csproj?

[MariusStorhaug]

Lets just say it wasnt an optimal build process I was using... My local windows machine :)
Changed it to be the runners... Now its green all over :)

Thanks all for the willingness to help!