-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
teleport 16.0.1 #175830
teleport 16.0.1 #175830
Conversation
Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request. |
0f85990
to
6c10d5b
Compare
|
Thanks for the PR, I agree we're stuck with |
6c10d5b
to
2a1e5a5
Compare
Sorry, I force pushed a change (before I saw that you had commented and kicked off another CI run) in an attempt to fix the Here is the change: ifeq ("$(OS)-$(ARCH)","darwin-arm64")
# Temporary link flags due to changes in Apple's linker
# https://github.com/golang/go/issues/67854
GO_LDFLAGS += -extldflags=-ld_classic
endif So I suppose this makes xcode a build dependency on darwin, but only on arm64? Need to figure out how to represent this in the formula though. |
2a1e5a5
to
18f0408
Compare
Linux runs out of disk space and I suspect macOS 12 doesn't have a new enough CLang to recognise that flag. |
Yep, seems like the only solution is to mark macOS 12 as broken and not build it? |
Could you ask upstream if building with Xcode 14 is still supposed to be supported? Because that would clarify if we should restrict it or patch it. |
According to the installation instructions, the minimal version of teleport is As we've noticed, they use a build flag that requires Xcode 15, which in turn requires macOS 13: And as far as I can tell, they only test/build on macos 13: To me this means that xcode 15 is required to build the binaries, but the resulting binaries will run on any macOS version above |
No, Homebrew bottles are only build for the OS they are building on. But it would be good to ask upstream what the idea is. They might not know they broke older builds, so if we ask they can patch it. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
For users wanting the latest
|
Seems like the |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?brew audit
fails with the following message:But if I swap from
rustup-init
torust
, the build fails becausewasm-pack
cannot find the wasm32-unknown-unknown target. As such I stuck withrustup-init
and added a comment which explains why (I believe) it is required.