nixpkgs/pkgs
Doron Behar f59f04352a ruby: Rename removeReferencesToCC flag to !jitSupport
If JIT support is built in to ruby, there's no choice other then to
leave this cc reference as is. removeReferencesToCC didn't do it's job
completely since some time ago. That's why it was practically redundant
- `lib/ruby/${version}/<platform>/rbconfig.rb` still referenced cc.
Removing this reference from
`lib/ruby/${version}/<platform>/rbconfig.rb` as well might lead to
breakage in some Gems that require this feature.

But, if JIT support is not desired, it should be safe enough to
completely remove all cc references, both in
lib/ruby/${version}/<platform>/rbconfig.rb and in $out/lib/libruby.so .
Hence now `rubyMinimal` has JIT support disabled and it has no
references at all to stdenv.cc.
2020-11-09 16:17:39 +02:00
..
applications Merge staging-next into staging 2020-11-09 14:49:10 +01:00
build-support docker: add final newline to detjson.py 2020-11-09 11:39:28 +00:00
common-updater scripts/mark-broken: improve 2020-10-30 23:11:36 -07:00
data Merge staging-next into staging 2020-11-09 14:49:10 +01:00
desktops Merge master into staging-next 2020-11-09 14:33:52 +01:00
development ruby: Rename removeReferencesToCC flag to !jitSupport 2020-11-09 16:17:39 +02:00
games keen4: add final newline to builder.sh 2020-11-09 11:39:28 +00:00
misc Merge master into staging-next 2020-11-09 14:33:52 +01:00
os-specific Merge master into staging-next 2020-11-09 14:33:52 +01:00
pkgs-lib pkgs-lib/tests/formats: improve message on failure 2020-10-19 21:46:08 +02:00
servers Merge master into staging-next 2020-11-09 14:33:52 +01:00
shells Merge master into staging-next 2020-11-09 14:33:52 +01:00
stdenv Merge staging-next into staging 2020-11-09 14:49:10 +01:00
test Recover the complicated situation after my bad merge 2020-10-26 09:01:04 +01:00
tools Merge master into staging-next 2020-11-09 14:33:52 +01:00
top-level ruby: Rename removeReferencesToCC flag to !jitSupport 2020-11-09 16:17:39 +02:00