-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
macOS compilation failures (brew, macports, and cmake) #3180
Comments
Mac M3 Air - sadly, clearing brew's cache didn't help. It did alter the log a bit though. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
@Pheggas |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
For whatever reason, this is still not working for me |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Thanks!
|
I have the same problem, full log indicates issue in gtest.h file:
Full log: 02.make.txt |
For everyone with the include problem, you have to reinstall Xcode command line tool the hard way. You have to do: |
FYI, for those still on macOS-12: #3236 |
This fixed my issue |
My error is the same as yours, Stuck in "target web ui", and update xcode did not work for me, macbook m3 with Sequoia 15.0 |
Is it possible to release formula Bottles for this Tool? |
I think it's possible. I would need some guidance on how to publish them. |
Tried clearing cache and reinstalling xcode, still cannot install with Seeing "Undefined symbols for architecture arm64" in the logs |
This comment was marked as abuse.
This comment was marked as abuse.
Please act professionally here. First and only warning. |
This comment was marked as abuse.
This comment was marked as abuse.
> username is "NeverBeLazy" lol |
btw just wanna ask, is the ARM version for Apple Silicon support HEVC hardware encode? if so is it supposed to have 70% GPU util on M1? running the x64 version because ARM version of the beta still isn't compiling for me and everytime im streaming its using 70% GPU and has noticable input lag, probably due to the translation layer |
As far as I know, it should. If you're emulating a different architecture it makes sense to consume more resources. Did you try this? #3180 (comment) |
Haven't, will do later today, thx for the tip |
Still got an error, i will open an issue at https://github.com/lizardbyte/homebrew-homebrew/issues, error is different from #3180 (comment) Nvm your homebrew repo doesn't have an issue section. Error is as follows, i don't know how to get more detailed make log
|
No need to open an issue in that repo since it will need to be fixed here |
I'm also getting @le0-VV's error after trying the various proposed solutions in this thread. I'm running macOS Sequoia 15.2 Beta (24C5079e), in case that's helpful. |
I recently upgraded Sequoia from Mac Sonoma. Homebrew had installed formulas into an 'alternative directories' instead of /usr/local/Cellar What ended up solving 'Exactly' the issue... Was uninstalling Hombrew with : /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)" as per :https://mac.install.guide/homebrew/5. then the few other files/ terminal suggests Then reinstalling homebrew and sunshine-beta .... : sudo rm -rf "$(brew --cache --build-from-source sunshine-beta)" THEn Sunshine-beta builds Again with CMake... |
Yeah that makes sense. ARM version of homebrew is installed to somewhere in /opt. I have x64 version of homebrew installed to /usr/local, maybe that’s why I can get sunshine installed in my x64 environment. But having to reinstall homebrew twice and change all their paths and whatnot is a pretty massive operation tho… |
This discussion on HOMEbrew git provided some insight. https://github.com/orgs/Homebrew/discussions/3316 |
This worked for me. Thank you! |
I tried to install sunshine-beta on MAC M2 many times but always minded me lose some dependencies ==> Installing sunshine-beta from lizardbyte/homebrew If reporting this issue please do so at (not Homebrew/brew or Homebrew/homebrew-core): |
@ayaka-ayaka-ayaka Same problem for me on Mac mini M4, running Sequoia 15.1.1 (24B2091). |
Some new issues starting today, should be fixed by #3457 |
This comment was marked as duplicate.
This comment was marked as duplicate.
If you want to brew from PR-branch: It will now build from that branch, which fixed those errors for me. Or you can simply wait until that PR is being merged into the master branch. IDK what the timeline is for that though. |
It's already merged |
查找... Unfortunately, these don't work for me |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
Several reports of macOS build failures. Consolidating into one issue.
Expected Behavior
No response
Additional Context
For brew, this may be resolved by clearing brew's cache. See Brew install sunshine but "CMake Generate step failed." #2369 (comment)
stable
sudo rm -rf "$(brew --cache --build-from-source sunshine-beta)"
beta
sudo rm -rf "$(brew --cache --build-from-source sunshine)"
Then install the beta version (v0.23.1 is unlikely to compile at this point without patches)
Host Operating System
macOS
Operating System Version
12+
Architecture
arm
Sunshine commit or version
v0.23.1+
Package
n/a
GPU Type
Apple Silicon
GPU Model
GPU Driver/Mesa Version
Capture Method
AVCaptureScreen (macOS)
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: