issue with packaging 'rustscan'

[Simon Tournier]

Hi,

On Sun, 21 May 2023 at 22:35, Timothy Washington <twashing@gmail.com> wrote:

> guix build -L ~/dotfiles/ rust-rustscan

[...]

>  error: failed to run custom build command for `ring v0.16.20`
>
> Caused by:
>   process didn't exit successfully: 
> `/tmp/guix-build-rust-rustscan-2.1.1.drv-0/rustscan-2.1.1/target/release/build/ring-9bf05aa562ef9c86/build-script-build`
>  (exit status: 101)
>   --- stderr
>   running "perl" "crypto/fipsmodule/aes/asm/aesni-x86_64.pl" "elf" 
> "/tmp/guix-build-rust-rustscan-2.1.1.drv-0/rustscan-2.1.1/target/release/build/ring-297f46c71994a65c/out/aesni-x86_64-elf.S"
>   thread 'main' panicked at 'failed to execute ["perl" 
> "crypto/fipsmodule/aes/asm/aesni-x86_64.pl" "elf" 
> "/tmp/guix-build-rust-rustscan-2.1.1.drv-0/rustscan-2.1.1/target/release/build/ring-297f46c71994a65c/out/aesni-x86_64-elf.S"]:
>  No such file or directory (os error 2)', 
> /tmp/guix-build-rust-rustscan-2.1.1.drv-0/rustscan-2.1.1/guix-vendor/rust-ring-0.16.20.tar.xz/build.rs:653:9
>   note: run with `RUST_BACKTRACE=1` environment variable to display a 
> backtrace
> warning: build failed, waiting for other jobs to finish...
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "cargo" arguments: ("build" "--release") 
> exit-status: 101 term-signal: #f stop-signal: #f>
> phase `build' failed after 12.2 seconds
> command "cargo" "build" "--release" failed with status 101
> builder for 
> `/gnu/store/x695f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv' failed 
> with exit code 1
> build of /gnu/store/x695f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv 
> failed
> View build log at 
> '/var/log/guix/drvs/x6/95f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv.gz'.
> guix build: error: build of 
> `/gnu/store/x695f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv' failed

The issue is that the Rust package named 'ring' cannot be built.
Since I am not an expert about Rust packaging, I do not know why and
how to fix this.  Well, one needs to put their hand in dirty Rust
packaging ;-)


Cheers,
simon