From: Tobias Kortkamp <tobias.kortkamp@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Timothy Washington <twashing@gmail.com>, guix-devel@gnu.org
Subject: Re: issue with packaging 'rustscan'
Date: Mon, 22 May 2023 11:56:17 +0200 [thread overview]
Message-ID: <87pm6sisi0.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ3OOgkRcPWQ2_8e_0ODLDC--kryY5=_20_w_WzJ8zTi0Q@mail.gmail.com>
Simon Tournier <zimon.toutoune@gmail.com> writes:
> 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 ;-)
Hello,
usually this error ("failed to execute" + "No such file or directory")
means that some build dependency is missing. In this case the build
script (build.rs) fails to run "perl
crypto/fipsmodule/aes/asm/aesni-x86_64.pl" to generate an assembly file.
Solution: add perl to native-inputs.
Best regards,
Tobias
next prev parent reply other threads:[~2023-05-22 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAADtM-b6Fpv9DPCRV_5ji+GBSESODOqL-SOEQh-G=6bL0XEetg@mail.gmail.com>
[not found] ` <875y8oz4ab.fsf@gmail.com>
[not found] ` <CAADtM-bc9FU6B+k5UaJctk3+T2aPO_z2edp=SM5LoZgd5JeNYA@mail.gmail.com>
2023-05-21 16:46 ` Howto reference a custom package from a manifest Simon Tournier
2023-05-21 20:35 ` Timothy Washington
2023-05-22 8:41 ` issue with packaging 'rustscan' Simon Tournier
2023-05-22 9:56 ` Tobias Kortkamp [this message]
2023-05-22 20:21 ` Timothy Washington
2023-05-22 18:17 ` Howto reference a custom package from a manifest Kaelyn
2023-05-22 20:20 ` Timothy Washington
2023-05-23 16:39 ` Kaelyn
2023-05-24 20:25 ` Timothy Washington
2023-05-24 22:16 ` Kaelyn
2023-05-26 23:27 ` Timothy Washington
2023-05-23 16:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-24 20:10 ` Timothy Washington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm6sisi0.fsf@gmail.com \
--to=tobias.kortkamp@gmail.com \
--cc=guix-devel@gnu.org \
--cc=twashing@gmail.com \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).