[ruby-core:62444] [ruby-trunk - Bug #9760] mkmf does not allow for linking against custom libraries when a system library is present

Issue #9760 has been updated by Akinori MUSHA.


In the meantime, third parties can work around this problem by a monkey patch like this:

https://github.com/sparklemotion/nokogiri/commit/c98745d9098487c51685a732f1c5a21d8d07cdad

----------------------------------------
Bug #9760: mkmf does not allow for linking against custom libraries when a system library is present
https://bugs.ruby-lang.org/issues/9760#change-46592

* Author: Andrew DeMaria
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Hi,

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)

---Files--------------------------------
fix_default_libpath.diff (1.2 KB)


-- 
https://bugs.ruby-lang.org/