* gnu/packages/crates-io.scm (rust-bindgen-0.57)[arguments]: Do not skip
build; disable tests; add development inputs rust-clap-2, rust-diff-0.1, and
rust-shlex-0.1.
[inputs]: Add clang.
* gnu/packages/crates-io.scm (rust-backtrace-0.3): Update to 0.3.66.
[arguments]: Replace rust-addr2line-0.14 with rust-addr2line-0.17,
rust-miniz-oxide-0.4 with rust-miniz-oxide-0.5, and rust-object-0.23 with
rust-object-0.29; add rust-libloading-0.7 and rust-cc-1; remove
rust-backtrace-sys-0.1.
* gnu/packages/crates-io.scm (rust-memmap2-0.5): Update to 0.5.5.
[arguments]: Do not skip build. Add rust-owning-ref-0.4 and rust-tempfile-3
to inputs.
* gnu/packages/crates-io.scm (rust-scroll-0.10): Update to 0.10.2.
[arguments]: Do not skip build; add cargo development inputs rust-byteorder-1
and rust-rayon-1.
* gnu/packages/crates-io.scm (rust-bio-types-0.12): Update to 0.12.1.
[arguments]: Replace rust-petgraph-0.5 with rust-petgraph-0.6, and replace
rust-strum-macros-0.20 with rust-strum-macros-0.21.
* gnu/packages/crates-io.scm (rust-itertools-0.10): Update to 0.10.1.
[arguments]: Do not skip build; add rust-criterion-0.3, rust-paste-1,
rust-permutohedron-0.2, rust-quickcheck-0.9, and rust-rand-0.7 to development
inputs.
* gnu/packages/tex.scm (texlive-caption): Update description.
[description]: newfloat.sty and totalcount.sty are not in the package.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
* gnu/packages/password-utils.scm
(hashcat)[native-inputs]: Move to ...
(hashcat)[inputs]: ... here.
(hashcat)[arguments]<#:make-flags>: Set AR and CC.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This is required for cross-compilation, as %output does not exist when
cross-compiling.
* gnu/packages/password-utils.scm (hashcat)[arguments]: Rewrite with G-exps.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
There does not appear to be a convenient Guix package for LZMA-SDK yet.
I currently have a bit of a dirty working tree (fiddling with imports), so the
use-modules is in the wrong place. Also, a small rebase conflict, the version
and source hash of hashcat has been updated.
* gnu/packages/password-utils.scm (hashcat)[source]{snippet}: Delete
everything from deps except for deps/LZMA-SDK.
(hashcat)[inputs]: Add minizip, xxhash and zlib.
(hashcat)[arguments]<#:make-flags>: Add USE_SYSTEM_ZLIB, USE_SYSTEM_OPENCL and
USE_SYSTEM_XXHASH.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This patch uses the 'pbarch' support added to 'racket-vm-cs' to make it
the default Racket VM implementation on all systems.
* gnu/packages/racket.scm (racket-vm-for-system): Remove.
(racket-minimal, racket)[inputs]: Replace '(racket-vm-for-system)' with
'racket-vm-cs'.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
This is an attempt to avoid a problem with Racket BC on ppc64 reported
in <https://issues.guix.gnu.org/57050#19> that was exposed by attempting
to use Racket BC to bootstrap Chez Scheme. Thanks to Matthew Flatt for
the workaround: <https://racket.discourse.group/t/950/30>.
* gnu/packages/racket.scm (racket-vm-bc)[arguments]<#:configure-flags>:
Increase the number of bytes that should be available on the stack for
"safety" when checking for stack overflow.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
On systems for which Racket's variant of Chez Scheme cannot generate
native code, it can use a 'pbarch' machine type: a variant of the
``portable bytecode'' backend specialized to word size and endianness.
This allows Racket CS to replace Racket BC on those systems while
maintaining comparable performance. (Racket BC lacks JIT support for
those systems anyway.) It also lets us provide a Chez Scheme package on
all systems Guix supports.
This patch adds 'pbarch' support to both 'chez-scheme-for-racket' and
'racket-vm-cs', but it does not change the Racket VM implementation used
for the 'racket' and 'racket-minimal' packages.
* gnu/packages/chez.scm (nix-system->pbarch-machine-type): New variable.
(chez-scheme-for-racket)[inputs]: Use 'libffi' for non-native systems.
[arguments]<#:configure-flags>: Always supply '-m='. Add applicable
flags for non-native systems.
[supported-systems]: Use '%supported-systems'.
[description]: Update.
(chez-scheme-for-racket-bootstrap-bootfiles)[arguments]<#:phases>: Adapt
'build' phase for non-native systems.
* gnu/packages/racket.scm (racket-vm-bc)[description]: Update.
(racket-vm-cs)[description]: Likewise.
[inputs]: Use 'libffi' for non-native systems.
[arguments]<#:configure-flags>: Add applicable flags for non-native
systems.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Cross-compilation works for 'racket-vm-cgc', 'racket-vm-bc', and
'racket-vm-cs'. These changes are not enough to cross-compile
'racket-minimal' or 'racket': that would require building and loading
cross-compilation pluggins for 'racket-vm-cs', which will be much
easier once we can build the package 'raco-cross'.
* gnu/packages/racket.scm (racket-vm-cgc): Add 'this-package' when
cross-compiling.
(racket-vm-bc)[native-inputs]: Adjust accordingly.
(racket-vm-cs)[native-inputs]: Use 'racket-vm-cs' instead of
'racket-vm-bc' when cross-compiling. Adapt to changes to
'racket-vm-cgc'.
[arguments]<#:configure-flags>: Fix '--enable-scheme' for
cross-compilation.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
* gnu/packages/chez.scm (racket-cs-native-supported-system): Change to
return the applicable machine type instead of '#t'.
(chez-scheme-for-racket)[native-inputs]: When cross-compiling, add
'this-package'.
[arguments]<#:configure-flags>: When cross-compiling, supply '-m=' and
'--toolprefix='.
<#:phases>: Work around cross-compilation issues in 'build' and
'install-docs'.
(chez-scheme-for-racket-bootstrap-bootfiles): When cross-compiling,
use 'zuo' and 'chez-scheme-for-racket' instead of 'racket-vm-bc'.
[arguments]<#:phases>: Adapt 'build' phase for cross-compilation.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
