search

simonjwright / alire-index.mac

Index of Alire crate versions catering for macOS idiosyncrasies
Apache License 2.0
6 stars 1 forks source link

macOS and Windows build servers are broken. #4

Open pmunts opened 5 months ago

pmunts commented 5 months ago

Apologies if this is the wrong place; there doesn't seem to be anywhere else to report alr build server errors.

I had to modify my remoteio and mcp2221 crates for alr 2.0 (pulls #1041 and #1042). Merging them into the index is currently blocked by build errors on the macOS and Windows build servers that are unrelated by the crates themselves, both of which I can build successfully on my local machines.

macOS:

The system package 'hidapi' is about to be installed.
This action might require admin privileges and impact your system installation.
Do you want Alire to install this system package?
Using default: Yes
Error: Cannot install under Rosetta 2 in ARM default prefix (/opt/homebrew)!
To rerun under ARM use:
    arch -arm64 brew install ...
To install under x86_64, install Homebrew into /usr/local.
stderr: Command ["brew", "install", "hidapi"] exited with code 1

Windows:

stderr: Command ["gnat", "--version"] exited with code -1
ERROR: Command ["gnat", "--version"] exited with code -1
Building with ...
Note: Running post-fetch actions for remoteio=2.22299.1...
Note: Building remoteio=2.22299.1/remoteio.gpr...
stderr: Cannot locate gprbuild, please check that you have a GNAT and GPRbuild installation in your environment.
ERROR: Cannot locate gprbuild, please check that you have a GNAT and GPRbuild installation in your environment.
stderr: ALIRE.CHECKED_ERROR
stderr: Cannot locate gprbuild, please check that you have a GNAT and GPRbuild installation in your environment.
simonjwright commented 5 months ago

I've found that commenting on the failing alire-index PR gets a response (not always immediately!)

I've not looked at the Windows issue, but on macOS I believe it's that Github have quietly updated the macos-latest runner to macos-14, i.e. Apple silicon; and the job picks up the latest alr it knows about, which is an Intel build. Hence confusion.

What I don't understand is why the Macports job succeeded.

I'll go and comment on these lines on the PR.