When building rbx with the same path settings as an already- installed rbx, it now uses the former and not the latter to build the gems. Important to have for packaging.
See #2915 for more information.
In the past we wrongly used the C linker so we ended up with these libraries explicitly linked. We now properly link C++ code with CXX. This means we don't need to explicitly link the C++ standard library. This also fixes issues with FreeBSD which has switch to clang / libc++ as the default instead of libstdc++. Also see #2900
uninitialized constant Find for rake todo task
- fix -> require find
In Rakefile, rakelib/gems.rake, rakelib/install.rake
There are a lot of sockets constants that were missing in Rubinius. This commit adds all of them to harmonize with the newest version of Ruby. After run platform.rake a new platform.conf file will be generated with the right values for the current operational system. Fixes #2729, rubysl/rubysl-socket#2 and enables to fix puma/puma#393
Tarballs will include .gem files for the build ruby. This enables using 'bundle install --local' to build packages for Rubinius offline.
The issue is that when you configure with --prefix, running 'rake' will install. Now the place that Rubinius was configure to run has a complete runtime directory structure. So when you start up rbx during the build process with a subsequent 'rake install', rbx will find the installed dirs, except we don't install the .rbc files because these are cached during runtime in ~/.rbx if at all. Short story is, 'rake; rake install' is redundant. Probably need to fix rake install to note that rbx is already installed or something.