Project

General

Profile

Bug #9760

mkmf does not allow for linking against custom libraries when a system library is present

Added by zanegray (Andrew DeMaria) over 6 years ago. Updated over 4 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]
[ruby-core:62100]
Tags:

Description

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) fix_default_libpath.diff zanegray (Andrew DeMaria), 04/19/2014 10:12 PM
early-libdir.patch (1.24 KB) early-libdir.patch sorah (Sorah Fukumori), 08/27/2015 05:18 PM

Also available in: Atom PDF