From: Brendan Tildesley via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "48373@debbugs.gnu.org" <48373@debbugs.gnu.org>
Cc: Christopher Howard <christopher@librehacker.com>
Subject: bug#48373: vice: processor dependency
Date: Wed, 12 May 2021 17:08:06 +0200 (CEST) [thread overview]
Message-ID: <802557135.259431.1620832086709@office.mailbox.org> (raw)
In-Reply-To: <75ca48e183a530adfab067d3ab703df61d5e919e.camel@librehacker.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
I'm curious the guix version would also build differently on your computer.
You can run for example
guix build vice --no-grafts --check
to build it from source and check the difference. if its different, something like
guix gc -D $(guix build --no-grafts vice); guix build --no-substitutes vice
should delete it and built it from source without using the prebuilt binary.
If it's different then its a reproducibility bug. Some packages are actually
intended to be that way, like atlas, and have substitutable? #f set so that
they are always built and tuned to the cpu it's used on.
On my computer, AMD 5700X, the built is identical to the substitute:
b@jiu ~/code/guix [env]$ guix challenge vice
1 store items were analyzed:
- 1 (100.0%) were identical
- 0 (0.0%) differed
- 0 (0.0%) were inconclusive
[-- Attachment #2: Type: text/html, Size: 1944 bytes --]
next prev parent reply other threads:[~2021-05-12 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 2:33 bug#48373: vice: processor dependency? Christopher Howard
2021-05-12 13:44 ` Christopher Howard
2021-05-12 15:08 ` Brendan Tildesley via Bug reports for GNU Guix [this message]
2021-05-12 15:30 ` bug#48373: vice: processor dependency Christopher Howard
2021-05-12 15:38 ` Brendan Tildesley via Bug reports for GNU Guix
2021-05-12 16:21 ` bug#48373: vice: processor dependency? Leo Famulari
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=802557135.259431.1620832086709@office.mailbox.org \
--to=bug-guix@gnu.org \
--cc=48373@debbugs.gnu.org \
--cc=btild@mailbox.org \
--cc=christopher@librehacker.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).