From: onur@... Date: 2016-05-24T08:11:27+00:00 Subject: [ruby-core:75700] [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 Onur K������k. We have a system where * Ruby 1.8.7-p374 is installed system wide from distribution packages * There is a user setup with RVM to run Ruby 2.x running Redmine with Mysql During Redmine bundle install, mysql2 gem is linking against the system Ruby, leading to issues like missing symbols etc. for the generated SO. The issue is happening with 2.2.3, 2.2.4 and 2.3.0 but it seems it is fixed in 2.3.1. I did not bisect but r52267 is probably what fixed it, thank you ! ---------------------------------------- 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-58832 * Author: Andrew DeMaria * Status: Open * Priority: Normal * Assignee: * ruby -v: ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: REQUIRED, 2.2: REQUIRED ---------------------------------------- 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) early-libdir.patch (1.24 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: