-
Notifications
You must be signed in to change notification settings - Fork 11
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
Does not build on macOS 14 / aarch64 #10
Comments
Oh wait, why does it even use |
This also fails on FreeBSD, similar problem:
gcc13-13.3.0 This seems to be a relatively common issue arising from a variation in library structure between BSD-based OSes and Linux based ones. |
something like this: |
@gessel This will break it for macOS when Those |
The process in bundler is entirely automatic and the compilers available are GCC13 and LLVM/Clang 15. The compilers don't know what to do. The solution proposed is to detect the OS and it sounds like the conditional should be for *BSD leaving Dawin/MacOS to work as it does (assuming it does). Strangely, FreeBSD has a port, https://www.freshports.org/databases/ruby-xapian/ which installs fine, but the gem install process seems to ignore the existing. The gem vs. ports management of Ruby gems seems to cause some issues here and there and perhaps that's a solution path. For example:
But, and this looks like it might be not the desired result:
|
I believe this has been fixed upstream. |
Building
xapian-ruby
from rubygems fails on Sonoma. Moreover, something seems to hardcode C++ runtime, which cannot work in default macOS setups:By default most of macOS versions (but not all) use
libc++
, so trying to link againstlibstdc++
will break stuff. (Hardcodinglibc++
will be wrong either, compiler should decide which runtime to use, it is done automatically.)As of now, linking is broken:
Xapian bindings for Ruby do build fine from the port, for example, so there is no inherent reason for them not to work. Just something goes wrong during the build here.
The text was updated successfully, but these errors were encountered: