From: "Ludovic Courtès" <ludo@gnu.org>
To: Jean-Baptiste Note <jean-baptiste.note@m4x.org>
Cc: 44337-done@debbugs.gnu.org
Subject: bug#44337: [squid] Reproducibility bug in squid package
Date: Mon, 02 Nov 2020 14:38:50 +0100 [thread overview]
Message-ID: <87a6vznaj9.fsf@gnu.org> (raw)
In-Reply-To: <87wnz7ph4h.fsf@m4x.org> (Jean-Baptiste Note's message of "Fri, 30 Oct 2020 20:56:46 +0000")
Hi Jean-Baptiste,
Jean-Baptiste Note <jean-baptiste.note@m4x.org> skribis:
> The squid package as provided from substitute servers currently crashes
> on my (admittedly old) Core 2 Duo server. Though generally observed in
> a different context (virtualization), this is an FAQ from SQUID -- see:
>
> https://wiki.squid-cache.org/KnowledgeBase/IllegalInstructionError
>
> I think the fix of disabling -march=native should actually be applied.
> In the current state, not only does the package not work on some x86_64
> machines, but the outcome of the build depends on the builder machine
> and thus defeats reproducibility.
Indeed. Our goal is to provide “generic” binaries, so disabling
‘-march=native’ is the right thing anyway.
> NB: maybe a more general fix could be envisionned for these kind of
> -march=native issues; this is admittedly a pretty local fix.
In practice it seems that packages rarely do that by default (with
linear algebra software being an exception), though I don’t have hard
figures.
>>From 199ca1036197064d609a8f76a7eb46b6e72996fb Mon Sep 17 00:00:00 2001
> From: Jean-Baptiste Note <jean-baptiste.note@m4x.org>
> Date: Wed, 28 Oct 2020 11:22:39 -0400
> Subject: [PATCH] gnu: squid: Fix build reproducibility issue.
>
> * gnu/packages/networking.scm (squid): Add --disable-arch-native configure
> flag.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2020-11-02 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 20:56 [bug#44337] [squid] Reproducibility bug in squid package Jean-Baptiste Note
2020-11-02 13:38 ` Ludovic Courtès [this message]
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=87a6vznaj9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44337-done@debbugs.gnu.org \
--cc=jean-baptiste.note@m4x.org \
/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).