Kevin Burke

I've verified that this works on Linux installing to a temporary directory.

Here's the script I have currently... ```bash install_ruby() { set -x local -r numcpu=$(grep -c ^processor /proc/cpuinfo) if [[ "${numcpu}" == '' ]]; then numcpu='1' fi pushd /tmp git clone...

Another option would be to tell people using `DESTDIR` that they're on their own and skip the post-install `RUBY_BIN` verification steps. Then you wouldn't need to set RUBYLIB etc.

Oh... basically it would be to just add a bit before every invocation of RUBY_BIN (for example verify_config) that skips running the command if DESTDIR is set.

Another issue with this patch I am noticing now that 2.7.1 has been released: This patch sets RUBYLIB to e.g. ``` $DESTDIR/usr/local/lib/ruby/2.7.1:$DESTDIR/usr/local/lib/ruby/2.7.1/x86_64-linux ``` However, Ruby installs the directories for 2.7.1...

> I'm not sure if we could reliably parse MAKE_INSTALL_OPTS to learn about DESTDIR. Agreed. I think the better approach would be to add a configuration option and then append...

Here's the patch I have right now: https://github.com/meterup/ruby-build/commit/74cad0e158e65c67c3d08ed2e88984451020a217 The `$RUBY_BIN` post-verify scripts fail unless we set RUBYLIB as e.g. ``` LD_LIBRARY_PATH=/tmp/releases/2.7.0/usr/local/ruby/lib RUBYLIB=/tmp/releases/2.7.0/usr/local/ruby/lib/ruby/2.7.0/:/tmp/releases/2.7.0/usr/local/ruby/lib/ruby/2.7.0/x86_64-linux/ /tmp/releases/2.7.0/usr/local/ruby/bin/ruby -e "puts 'hi'" ``` I'm not sure...

Another option would be a way to figure out how to remove e.g. the verify scripts that run after Ruby is compiled.

I guess `LvlFromString` exists for this use case.

If I'm understanding this right we'd need to implement SSL_CTX_set_options and define/implement all of the bit fields that can be set, or make them no-ops if not supported. Here are...