MoltenVK-latest @1.2.9: Command failed: lipo -thin x86_64 libMoltenVK.A -o libMoltenVK.A 2> /dev/null

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/ports-11_x86_64-builder/builds/157259/steps/install-port/logs/stdio

DEBUG: Executing org.macports.destroot (MoltenVK-latest)
DEBUG: system -W /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_MoltenVK/MoltenVK-latest/work/destroot/opt/local/Library/Frameworks/MoltenVK.xcframework/macos-arm64_x86_64: lipo -thin x86_64 libMoltenVK.A -o libMoltenVK.A 2> /dev/null
Command failed: lipo -thin x86_64 libMoltenVK.A -o libMoltenVK.A 2> /dev/null
Exit code: 1

[Gcenx]

MoltenVK-latest

[Gcenx]

MoltenVK-1.1.9

[Gcenx]

As GitHub actions both MoltenVK-latest & MoltenVK-1.1.9 build locally without issue so I'm not sure why MoltenVK-latest would fail on the builbot.

[ryandesign (Ryan Carsten Schmidt)]

One difference between our Buildbot workers and GitHub Actions runners is that the former use case-sensitive file systems. Are all of your paths capitalized correctly?

[Gcenx]

Replying to ryandesign:

One difference between our Buildbot workers and GitHub Actions runners is that the former use case-sensitive file systems. Are all of your paths capitalized correctly?

That's the strange part all the paths are correct, I've attached a screenshot of this being installed locally where it shows as libMoltenVK.A

The only Big Sur (arm64) buildbot worked but shows this as /opt/local/Library/Frameworks/MoltenVK.xcframework/macos-arm64_x86_64/libMoltenVK.a, so should I change the Portfile to instead just expect that?

[ryandesign (Ryan Carsten Schmidt)]

Big Sur (arm64) does not exist anymore. Any Big Sur (arm64) logs you see are outdated.

[ryandesign (Ryan Carsten Schmidt)]

Replying to Gcenx:

Replying to ryandesign:

One difference between our Buildbot workers and GitHub Actions runners is that the former use case-sensitive file systems. Are all of your paths capitalized correctly?

That's the strange part all the paths are correct, I've attached a screenshot of this being installed locally where it shows as libMoltenVK.A

The screenshot shows what got installed into the destroot and from there was packaged into the port's binary archive, not what existed in the original distfile. Certainly if you tell the OS to copy a file and the case you use is not correct but your file system is case insensitive, then the copy will succeed and the copied file will have the new ("incorrect") case:

% mkdir foo bar
% touch foo/a
% cp foo/A bar 
% ls bar
A

The only Big Sur (arm64) buildbot worked but shows this as /opt/local/Library/Frameworks/MoltenVK.xcframework/macos-arm64_x86_64/libMoltenVK.a, so should I change the Portfile to instead just expect that?

It is libMoltenVK.a, with a lowercase "a" (as all static libraries are):

% sudo port extract  MoltenVK-latest
Password:
--->  Fetching distfiles for MoltenVK-latest
--->  Attempting to fetch MoltenVK-macos.tar from https://distfiles.macports.org/MoltenVK/1.2.9
--->  Verifying checksums for MoltenVK-latest                                        
--->  Extracting MoltenVK-latest
% find $(port work MoltenVK-latest) -iname libMoltenVK.A
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_MoltenVK/MoltenVK-latest/work/MoltenVK/MoltenVK/static/MoltenVK.xcframework/macos-arm64_x86_64/libMoltenVK.a

[Gcenx]

With that being the case it would be resolved with ​https://github.com/macports/macports-ports/pull/24121

[Dean M Greer <38226388+Gcenx@…>]

In 9a76c0f1f60a7256a0290b4876c535966d880b64/macports-ports (master):

MoltenVK: Set lower case for libMoltenVK.a

Closes: #70057