[Xapian-tickets] [Xapian] #837: Error compiling Ruby bindings with Ruby from Nixpkg
Xapian
nobody at xapian.org
Fri Apr 18 00:14:32 BST 2025
#837: Error compiling Ruby bindings with Ruby from Nixpkg
------------------------------------+---------------------------
Reporter: Graeme Porteous | Owner: (none)
Type: defect | Status: closed
Priority: normal | Milestone: 1.4.29
Component: Xapian-bindings (Ruby) | Version:
Severity: minor | Resolution: fixed
Keywords: | Blocked By:
Blocking: | Operating System: All
------------------------------------+---------------------------
Changes (by Olly Betts):
* status: new => closed
* resolution: => fixed
* milestone: => 1.4.29
Comment:
Oh sorry, I missed this when preparing 1.4.28 (released earlier today)
because I'd failed to set the milestone.
Thanks for the logs. They don't show use of any unusual linker options,
so it isn't that.
Digging a bit, I found https://github.com/ziglang/zig/issues/8180 which
seems to explain the situation - the one sentence summary is that macOS
defaults to not allowing undefined symbols in this case, but you can
select Linux-like behaviour with `-undefined dynamic_lookup`.
It looks like libtool should be turning this option on for us and I'm not
sure why that isn't working for you. I can see that macOS-specific probes
are getting run from your `configure.log`.
However looking at the handful of Debian-packaged Ruby modules I have
installed, they all are explicitly linked to libruby3.3 except for
`_xapian.so`, so it seems that linking to libruby''X.Y'' unconditionally
would better align us with Ruby norms so let's just do that.
Fix applied to git master in a3ef56cdda871cd2f6794ec50d686207a2032ae4 and
backported for 1.4.29 in
6062f0031dd72998e848e7e3577886be1b6be2c7. This should be functionally the
same as the patch you linked to above, but if you're able to easy test
please do.
--
Ticket URL: <https://trac.xapian.org/ticket/837#comment:4>
Xapian <https://xapian.org/>
Xapian
More information about the Xapian-tickets
mailing list