From: Adam Faiz <adam.faiz@disroot.org>
To: zimon.toutoune@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: package transformation and “guix graph”?
Date: Sat, 29 Apr 2023 08:08:52 +0800 [thread overview]
Message-ID: <cebb4a42-8bff-438d-764c-a06234473969@disroot.org> (raw)
Hello,
> Hi,
>
> Investigating « bug#62645: Failing `guix install gnash` » [1], I am a
> bit surprised:
>> The package rust-hmac needs to be rebuilt but it does not appear
> connected via “guix graph”. Note that rust-hmac has no direct
> dependency and only the ones from the Rust build system.
>
> Similarly, the node ’gcc’ appears in the DAG of gnash:
>
> but then,
>
> --8<---------------cut here---------------start------------->8---
> $ guix graph --path gnash -e '(@@ (gnu packages gcc) gcc-11)' -t bag
> guix graph: error: no path from 'gnash@0.8.11-0.583ccbc' to 'gcc@11.3.0'
> --8<---------------cut here---------------end--------------->8---
>
> And note that,
>
> --8<---------------cut here---------------start------------->8---
> $ guix build -e '(@@ (gnu packages gcc) gcc-11)' --no-grafts -d
> /gnu/store/rcd13s3lcd579s0l8v3awk4a6kbj8hvz-gcc-11.3.0.drv
> $ guix build -e '(@@ (gnu packages gcc) gcc-11)' -d
> /gnu/store/rcd13s3lcd579s0l8v3awk4a6kbj8hvz-gcc-11.3.0.drv
> --8<---------------cut here---------------end--------------->8---
>
> the derivation does not match with the one reported by “guix graph”.
>
>
> Last, the package ’gcc’ appears in the graph of ’rust-hmac’ – which
> seems weird to me but why not:
>
> --8<---------------cut here---------------start------------->8---
> $ guix graph rust-hmac -t bag-emerged | grep label | grep gcc
> "/gnu/store/wcx86bp6zcad2n2x5940dndhcksvfk5v-gcc-11.3.0.drv" [label =
> "gcc@11.3.0", shape = box, fontname = sans];
> --8<---------------cut here---------------end--------------->8---
>
> and then again no path between rust-hmac and gcc. Note the same
> derivation.
>
>
> What do I miss?
There's a long standing issue of rust packages not using inputs and native-inputs[1] because of how cargo-build-system works.
The WIP antioxidant-build-system[2] will properly address all the shortcomings currently in Guix's Rust packaging.
gcc-11 is an implicit input of gnu-build-system so it's still in the build graph.
1: https://issues.guix.gnu.org/53127
2: https://notabug.org/maximed/cargoless-rust-experiments
>
>
> Cheers,
> simon
>
> 1: https://issues.guix.gnu.org/issue/62645
next reply other threads:[~2023-04-29 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 0:08 Adam Faiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 17:00 package transformation and “guix graph”? Simon Tournier
2023-05-03 21:36 ` Ludovic Courtès
2023-05-04 8:18 ` Simon Tournier
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=cebb4a42-8bff-438d-764c-a06234473969@disroot.org \
--to=adam.faiz@disroot.org \
--cc=guix-devel@gnu.org \
--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).