Opened 4 weeks ago
Last modified 4 weeks ago
#74443 assigned defect
mas fails to build under mac os 27 "Golden Gate"
| Reported by: | MaurizioLoreti | Owned by: | judaew (Vadym-Valdis Yudaiev) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.12.6 |
| Keywords: | goldengate | Cc: | sierkb (Sierk Bornemann) |
| Port: | mas |
Description
as said. main.log attached.
Attachments (1)
Change History (6)
Changed 4 weeks ago by MaurizioLoreti
comment:1 Changed 4 weeks ago by jmroot (Joshua Root)
| Cc: | judaew removed |
|---|---|
| Keywords: | goldengate added |
| Owner: | set to judaew |
| Status: | new → assigned |
comment:2 follow-up: 3 Changed 4 weeks ago by rgoldberg (Ross Goldberg)
I'm the mas developer.
I've already fixed this problem locally on my personal Mac.
My initial fix might be backwards incompatible with older versions of Swift / Xcode, so I would probably need to tweak it for actual release.
Unfortunately, mas is set up for linear development, and the next release will take some time; see Details for more info.
TL;DR
Either:
- Build with Swift 6.3:
- Xcode 26.4-26.MAX
- Install a Swift 6.3 toolchain via Swiftly:
- I didn't find a Swiftly port, but, obviously, if I missed it, or if you create one, that will work
- https://www.swift.org/install/macos/
- brew install swiftly
- Install from precompiled binaries:
- I don't know if MacPorts has prebuilt binaries
- GitHub releases: https://github.com/mas-cli/mas/releases/tag/v7.0.0
- Homebrew Core mas formula bottles
Details
If mas were set up for release branches, etc., I could release the fix quickly.
I might revisit linear vs. release branch development later, but mas is in a fairly unique situation now.
After about 6 months or so, I imagine that most mas work should be relatively small.
Unfortunately, I am in the middle of numerous massive changes.
There are some changes in main that shouldn't be released.
They'll work, but they won't play nicely with sudoers.
I've fixed that locally, but some other changes must be made to allow that fix to work everywhere.
You don't want to know all the gory details.
Much tenuously, yet importantly, related work must be finished before I can release the next mas, which will take some time.
comment:3 Changed 4 weeks ago by ryandesign (Ryan Carsten Schmidt)
Replying to rgoldberg:
- brew install swiftly
Please do not have both Homebrew and MacPorts installed at the same time. They will interfere with one another and we will not support such a configuration.
- Install from precompiled binaries:
- I don't know if MacPorts has prebuilt binaries
MacPorts does provide precompiled binaries, but does not generally redistribute binaries compiled by someone else; we build our own. Since macOS 27 has only just been released, we've only just started building them, and it will take weeks to build all ports.
Also, a prerequisite for us providing a precompiled binary is that we can compile the software. If the reporter of this ticket could not compile it on macOS 27, our macOS 27 build machine probably won't be able to compile it either.
comment:4 Changed 4 weeks ago by rgoldberg (Ross Goldberg)
Can you either:
- Configure MacPorts build servers to use some Swift 6.3 toolchain on macOS 27, either via:
- An older version of Xcode?
- A Swift toolchain installed separately, possibly via Swiftly?
- Note: this might not fix anything, because the problem might be from the macOS SDK. I doubt that a non-Xcode Swift toolchain will have the macOS SDK, and I don't know if any older Xcode can install on macOS 27, or if they'd include an older SDK if installed. I haven't investigated this stuff as I've been able to get things working on my own Mac & GHA runners without investigating more thoroughly.
- Reuse the macOS 26 binaries for macOS 27?
comment:5 Changed 4 weeks ago by sierkb (Sierk Bornemann)
| Cc: | sierkb added |
|---|

main.log