mkmf does not allow for linking against custom libraries when a system library is present
|ruby -v:||ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]||Backport:||2.0.0: UNKNOWN, 2.1: REQUIRED|
Hopefully the title is not confusing, but the short story is that mkmf outputs a makefile that first searches the default lib path before searching any user provided lib paths. This is not an issue until one tries to link against an included library whose version is different than a preexisting system library.
The issue cropped up while trying to install the rugged gem (libgit2 wrapper) and a full dialog on the issue can be found on github https://github.com/libgit2/rugged/issues/351.
I was able to fix the issue with the attached patch (https://github.com/muff1nman/ruby/commit/a0c8bc32cfc11e61c5b9703bff243934c6509210)
mkmf.rb: prefer $LIBPATH than $DEFLIBPATH
- lib/mkmf.rb (link_command, libpathflag, create_makefile): prefer
$DEFLIBPATH. [ruby-trunk - Bug #9760]
#1 Updated by Nobuyoshi Nakada 10 months ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
#2 Updated by Akinori MUSHA 10 months ago
In the meantime, third parties can work around this problem by a monkey patch like this:
#3 Updated by Akinori MUSHA 9 months ago
The monkey patch I mentioned above was backed out due to a serious problem found, that is, if an instance of libruby.so (of the same soname as the running ruby) is found in a user-given path that is different from the one for the running ruby used for build, it will be picked by the linker and the resulted extension will cause a SEGV in run time.
So, it turned out DEFLIBPATH took precedence over LIBPATH for a good reason and I'm afraid it should not have been simply changed this way.