-
Notifications
You must be signed in to change notification settings - Fork 30
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
Recent MacOS compile problems with Objective C sources #431
Comments
unable to reproduce on our CI-builders (using Monterey). |
Which should be the same version as on Monterey, AFAICT. |
Maybe it's the compiler? I'm using clang (from Xcode) here:
Maybe I should install gcc from Homebrew and try again? |
I tried with gcc-14 from Homebrew, but that gives me compile errors early on. I also tried setting just OBJCXX in the environment, but that doesn't help either, it gives the same error as before. |
It looks like the issue might be with automake (1.16.5 in Homebrew), as the required |
OK, it seems that running I'm still wondering what the root cause of the issue is. Looks like some glitch in homebrew's automake 1.16.5 to me. In fact, it seems that the automake bottle was updated some 9 months ago, but I haven't compiled Gem manually for quite some time, so I'm not sure when this stuff started breaking for me. It's also curious that you don't see this issue on your CI. Do you run the same automake version from homebrew there? |
thanks for checking. i will investigate my CI (but most likely it is something along the lines of: "the VMs have some tools (like |
so here's what is actually used on our CI:
apparently we are using Here's how
Could you post the output (and input) of your |
another test, this time on my Sonoma VM:
again, the build succeeds:
|
Ok, over here I have autoreconf/autoconf/autoheader 2.72 and clang version 15.0.0 from Xcode 15.2, so there are some discrepancies to your setups. Attached is the output from |
I don't see anything suspicious in there. The config.log also looks fine -- g++ a.k.a. clang is properly recognized as capable of compiling Objective C++ source. And, as your logs indicate, the Maybe I just have an unlucky Xcode/autotools combination? But I'm also building Gem as a submodule of Purr Data on GH using the macos-12 runner, and it fails with exactly the same error. Ok, I should maybe try to update my MB to Sonoma and see whether that helps. If you have any idea what's going on there, that would be much appreciated. |
Detail
I'm now getting these compile errors on a MacBook Air M1, running macOS 13.6.7 (22G720) with the latest Xcode (Version 15.2 (15C500b)) and Homebrew. This all used to compile fine up to some months ago. Latest Gem source from the master branch now gives me this:
Looks like libtool suddenly doesn't know how to compile Objective C++ code any more. The rest of the compile up to this point goes fine. Gem was configured and built with:
Any help much appreciated, thanks!
Gem Version
1659d62
Pd Version
0.53-1
Operating System
macOS
OS Version
Ventura 13.6.7 (22G720)
Which CPU are you using?
arm64 ("64bit ARM"; e.g. Apple Silicon,...)
The text was updated successfully, but these errors were encountered: