[Bug ld/18448] New: Building Ruby gems with Bundler fails after binutils commit d4ae5fb0b5d1ae4270b3343509e8bd2d529aa291

[infoman1985 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=18448

            Bug ID: 18448
           Summary: Building Ruby gems with Bundler fails after binutils
                    commit d4ae5fb0b5d1ae4270b3343509e8bd2d529aa291
           Product: binutils
           Version: 2.25
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: infoman1985 at gmail dot com
  Target Milestone: ---

After updating to binutils-2.25 I found that after bundle install command in
one of my Ruby on Rails project it failed to start with en error message like:

/home/infoman/work/dev/binutils-bisect/bundler-test/vendor/bundle/ruby/2.0.0/gems/nokogumbo-1.4.2/lib/nokogumbo.rb:2:in
`require': nokogiri.so: cannot open shared object file: No such file or
directory -
/home/infoman/work/dev/binutils-bisect/bundler-test/vendor/bundle/ruby/2.0.0/extensions/x86-linux/2.0.0/nokogumbo-1.4.2/nokogumboc.so
(LoadError)

After some research I found that the old binutils added full path to
nokogiri.so, but in 2.25 it was just a library name that links to nowhere —
because nokogiri.so is only installed under bundler and is not in any of the
system paths.

Then git bisect led me to commit d4ae5fb0b5d1ae4270b3343509e8bd2d529aa291,
which changed behavior in -l:*.so processing.

For a testcase you can create a simple Gemfile with the following content:

source "https://rubygems.org";
gem 'nokogumbo'

Then run:
bundle install --path=vendor/bundle
bundle console

For binutils-2.24 this opens an IRB console with requested gems loaded to it.
For binutils-2.25, git master and possibly any revision starting from d4ae5fb
just an error message appears about nokogiri.so.

Is this a bug in binutils or possibly nokogumbo (and other gems with binary
extensions depending on another gems) must change something in their build
process?

-- 
You are receiving this mail because:
You are on the CC list for the bug.