summary refs log tree commit diff
path: root/pkgs/development/interpreters
Commit message (Collapse)AuthorAge
* evcxr: 0.4.6 -> 0.5.0Maximilian Bosch2020-01-23
| | | | https://crates.io/crates/evcxr/0.5.0
* Merge pull request #77991 from marsam/fix-pypy-darwinMario Rodas2020-01-22
|\ | | | | pypy: fix build on darwin
| * pypy: fix build on darwinMario Rodas2019-10-26
| |
* | perl.withPackages: respect $PERL5LIBvolth2020-01-20
| | | | | | perl.withPackages did not allow to add more packages using $PERL5LIB
* | treewide: Remove myself from maintainers on some packages (#78027)Ivan Kozik2020-01-19
|/
* wasmer: init at 0.13.0Oleksii Filonenko2020-01-16
|
* pythonPackages.venvShellHook: initFrederik Rietdijk2020-01-14
| | | | | This is a hook that loads a virtualenv from the specified `venvDir` location. If the virtualenv does not exist, it is created.
* perl: fix configure phase for Aarch32 (#76922)Jörg Thalheim2020-01-13
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In "perl: fuse configureFlags" [1] the effects of the preConfigure phase were merged into configureFlags. After this change values with spaces do not reach the configure script intact. The only flag this affects is `ldflags` for Aarch32 and Mips, and perl builds without it on armv7l-linux so it's probably no longer required on any platform. Fixes: configuring configure flags: -de -Dcc=cc <...> -Dldflags=\"-lm -lrt\" ./Configure: eval: line 1677: unexpected EOF while looking for matching `"' ./Configure: eval: line 1678: syntax error: unexpected end of file Configure: unknown option -lrt" [1] 3b50d0462a4174bb155b258a32ab1ab4176ba2fc
| * perl: fix configure phase for Aarch32Andrew Childs2020-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In "perl: fuse configureFlags" [1] the effects of the preConfigure phase were merged into configureFlags. After this change values with spaces do not reach the configure script intact. The only flag this affects is `ldflags` for Aarch32 and Mips, and perl builds without it on armv7l-linux so it's probably no longer required on any platform. Fixes: configuring configure flags: -de -Dcc=cc <...> -Dldflags=\"-lm -lrt\" ./Configure: eval: line 1677: unexpected EOF while looking for matching `"' ./Configure: eval: line 1678: syntax error: unexpected end of file Configure: unknown option -lrt" [1] 3b50d0462a4174bb155b258a32ab1ab4176ba2fc
* | joker: 0.12.9 -> 0.14.0R. RyanTM2020-01-10
| |
* | ruby: remove references to CC by defaultAlyssa Ross2020-01-09
| | | | | | | | | | This makes RbConfig["CC"] return an invalid path, but I hope nothing is depending on that anyway...
* | python: Add support for installing Python eggsadisbladis2020-01-08
| |
* | Merge pull request #77181 from r-ryantm/auto-update/picoLispMichael Raskin2020-01-08
|\ \ | | | | | | picolisp: 19.6 -> 19.12
| * | picolisp: 19.6 -> 19.12R. RyanTM2020-01-06
| |/
* | wasmtime: 20191111 -> v0.8.0Joachim Breitner2020-01-07
| |
* | janet: 1.5.1 -> 1.6.0R. RyanTM2020-01-06
|/
* micropython: init at 1.12Stig Palmquist2020-01-03
|
* Merge master into staging-nextFrederik Rietdijk2020-01-02
|\
| * quickjs: 2019-10-27 -> 2019-12-21Austin Seipp2020-01-01
| | | | | | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
| * evcxr: 0.4.5 -> 0.4.6Maximilian Bosch2020-01-01
| | | | | | | | https://github.com/google/evcxr/releases/tag/v0.4.6
* | Merge master into staging-nextFrederik Rietdijk2019-12-31
|\|
| * Merge pull request #74090 from obsidiansystems/ghcjs-cross-without-ccJohn Ericson2019-12-30
| |\ | | | | | | stdenv, haskell: bonafied GHCJS cross compilation without stdenv.cc
| | * Merge remote-tracking branch 'upstream/master' into ghcjs-cross-without-ccJohn Ericson2019-11-25
| | |\
| | * | stdenv: Introduce hasCC attributeJohn Ericson2019-11-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before, we'd always use `cc = null`, and check for that. The problem is this breaks for cross compilation to platforms that don't support a C compiler. It's a very subtle issue. One might think there is no problem because we have `stdenvNoCC`, and presumably one would only build derivations that use that. The problem is that one still wants to use tools at build-time that are themselves built with a C compiler, and those are gotten via "splicing". The runtime version of those deps will explode, but the build time / `buildPackages` versions of those deps will be fine, and splicing attempts to work this by using `builtins.tryEval` to filter out any broken "higher priority" packages (runtime is the default and highest priority) so that both `foo` and `foo.nativeDrv` works. However, `tryEval` only catches certain evaluation failures (e.g. exceptions), and not arbitrary failures (such as `cc.attr` when `cc` is null). This means `tryEval` fails to let us use our build time deps, and everything comes apart. The right solution is, as usually, to get rid of splicing. Or, baring that, to make it so `foo` never works and one has to explicitly do `foo.*`. But that is a much larger change, and certaily one unsuitable to be backported to stable. Given that, we instead make an exception-throwing `cc` attribute, and create a `hasCC` attribute for those derivations which wish to condtionally use a C compiler: instead of doing `stdenv.cc or null == null` or something similar, one does `stdenv.hasCC`. This allows quering without "tripping" the exception, while also allowing `tryEval` to work. No platform without a C compiler is yet wired up by default. That will be done in a following commit.
* | | | treewide: *inputs are listsRobin Gloster2019-12-31
| | | |
* | | | ruby: installFlags is a listRobin Gloster2019-12-31
| | | |
* | | | treewide: installTargets is a listRobin Gloster2019-12-31
| | | |
* | | | treewide: NIX_*_FLAGS -> stringRobin Gloster2019-12-31
| | | |
* | | | treewide: NIX_*_FLAGS -> stringRobin Gloster2019-12-31
| | | |
* | | | treewide: NIX_*_COMPILE -> stringRobin Gloster2019-12-31
| | | |
* | | | python.pkgs.wrapPython: get rid of warningJan Tojnar2019-12-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When `makeWrapperArgs` variable is not set, `declare -p makeWrapperArgs` will return with 1 and print an error message to stderr. I did not handle the non-existence case in b0633406cb70e0e4ae3470a6b49e32b38d99ac16 because I thought `mk-python-derivation` will always define `makeWrapperArgs` but `wrapProgram` can be called independently. And even with `mk-python-derivation`, `makeWrappers` will not be set unless explicitly declared in the derivation because of https://github.com/NixOS/nix/issues/1461. I was lead to believe that because the builds were succeeding and I confirmed that the mechanism fails when the variable is not defined and `-o nounset` is enabled. It appears that `wrapPython` setup hook is not running under `-o nounset`, though, invaldating the assumption. Now we are checking that the variable exists before checking its type, which will get rid of the warning and also prevent future error when `-o nounset` is enabled in the setup hook. For more information, see the discussion at https://github.com/NixOS/nixpkgs/commit/a6bb2ede232940a96150da7207a3ecd15eb6328
* | | | rubygems: fix for Ruby with no opensslAlyssa Ross2019-12-30
| | | | | | | | | | | | | | | | This fixes the rubyMinimal package.
* | | | treewide: installTargets is a listRobin Gloster2019-12-30
| | | |
* | | | treewide: replace make/build/configure/patchFlags with nix listsMerijn Broeren2019-12-30
| | | |
* | | | perl: fuse configureFlagsRobin Gloster2019-12-30
| | | |
* | | | Merge branch 'staging-next' into stagingJan Tojnar2019-12-30
|\| | |
| * | | Merge branch 'master' into staging-nextJan Tojnar2019-12-30
| |\ \ \
| | * | | treewide: fix *FlagsRobin Gloster2019-12-30
| | | | |
* | | | | Merge staging-next into stagingFrederik Rietdijk2019-12-29
|\| | | |
| * | | | Merge master into staging-nextFrederik Rietdijk2019-12-29
| |\| | |
| | * | | ruby_2_7: init at 2.7.0Mario Rodas2019-12-25
| | | | | | | | | | | | | | | | | | | | Release notes: https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/
| | * | | ruby: rubygems 3.0.6 -> 3.1.2Mario Rodas2019-12-25
| | | | | | | | | | | | | | | | | | | | Changelog: https://blog.rubygems.org/2019/12/20/3.1.2-released.html
| | * | | rubyMinimal: ruby with all options disabled by defaultProfpatsch2019-12-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Similar to `gitMinimal` or `pythonMinimal`, this is useful for scripts which don’t use anything but the standard library and want a small footprint.
| | * | | ruby: add `removeReferenceToCC` package optionProfpatsch2019-12-25
| | | | | | | | | | | | | | | | | | | | Reduces the runtime closure by ~200MB if enabled.
* | | | | python.pkgs.wrapPython: fix string makeWrapperArgsJan Tojnar2019-12-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bash takes an assignment of a string to an array variable: local -a user_args user_args="(foo bar)" to mean appending the string to the array, not parsing the string into an array as is the case when on the same line as the declaration: local -a user_args="(foo bar)" b0633406cb70e0e4ae3470a6b49e32b38d99ac16 extracted the declaration before the newly branched code block, causing string makeWrapperArgs being added to the array verbatim. Since local is function scoped, it does not matter if we move it inside each of the branches so we fix it this way.
* | | | | Merge pull request #76283 from jtojnar/python-mwaworldofpeace2019-12-26
|\ \ \ \ \ | | | | | | | | | | | | python.pkgs.wrapPython: fix makeWrapperArgs
| * | | | | python.pkgs.wrapPython: fix makeWrapperArgsJan Tojnar2019-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When `makeWrapperArgs` is a Bash array, we only passed the first item to `wrapProgram`. We need to use `"${makeWrapperArgs[@]}"` to extract all the items. But that breaks the common string case so we need to handle that case separately.
* | | | | | Merge branch 'staging-next' into stagingJan Tojnar2019-12-25
|\ \ \ \ \ \ | | |/ / / / | |/| | | |
| * | | | | Merge branch 'master' into staging-nextJan Tojnar2019-12-25
| |\ \ \ \ \ | | | |/ / / | | |/| | |
| | * | | | erlang: build on aarch64-linuxworldofpeace2019-12-22
| | | | | | | | | | | | | | | | | | | | | | | | I've built several versions without issue.