Bug #13724
closedmake install does not install bundled gems
Description
I believe the usual way to build C (autoconf) software is
autoconf
./configure --prefix=...
make
make install
However, such a sequence does not download nor install bundled gems.
One needs to "make up" before "make install".
This is also not documented in "make help" nor in the README:
https://github.com/ruby/ruby#how-to-compile-and-install
As a consequence many people who build ruby from the source repository might get a ruby without the usual bundled gems (and therefore different from a release).
As an example, did_you_mean does not work without "make up":
$ ruby -e 'p [].eac'
Updated by Eregon (Benoit Daloze) almost 7 years ago
At first sight it seems the standard Homebrew ruby formula does not install bundled gems either due to this:
https://github.com/Homebrew/homebrew-core/blob/a71cdcd43814c8692718eca61bf67ef0b61cdf9e/Formula/ruby.rb#L75-L76
Updated by hsbt (Hiroshi SHIBATA) almost 7 years ago
installation of bundled gems requires make update-gems
and make extract-gems
.
We should add above instructions to README.md.
Updated by hsbt (Hiroshi SHIBATA) almost 7 years ago
- Status changed from Open to Assigned
- Assignee set to hsbt (Hiroshi SHIBATA)
Updated by hsbt (Hiroshi SHIBATA) over 6 years ago
- Status changed from Assigned to Closed
Applied in changeset trunk|r59962.
Added documentation
Added documentaiton for installation of bundled gems.
[Bug #13724][ruby-core:81938]
Updated by Eregon (Benoit Daloze) about 4 years ago
A few years later this still caught me as a big surprise:
https://github.com/ruby/openssl/pull/319#issuecomment-583781961
Most C software is fully built/installed with ./configure && make && make install
, why should Ruby be any different?