From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org, guix-hpc@gnu.org,
simon tournier <simon.tournier@univ-paris-diderot.fr>
Subject: Re: Reproducible Research Hackathon: Friday, July 3rd
Date: Mon, 13 Jul 2020 15:41:59 +0200 [thread overview]
Message-ID: <875zarr0pk.fsf@gnu.org> (raw)
In-Reply-To: <m13667ip5l.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Sat, 04 Jul 2020 11:51:34 +0200")
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> There is an interesting issue left for me to explore, which is why
> Python 2.4 compiled with today's gcc has a bug that it definitely didn't
> have back then. It's probably related to the many intentional
> ambiguities in the C language standard, check out John Regehr's blog
> (https://blog.regehr.org/) for interesting examples. That could become a
> selling point for Guix because we have the option of compiling old
> software with old compilers, which is hard with other infrastructures.
Apologies for the delay. What was this bug exactly?
I know Bonface addressed an issue related to how the Python 2.4 build
system would capture the kernel version via ‘uname’ a build time:
https://gitlab.inria.fr/guix-hpc/guix-past/-/commit/d1977f5dccd73341f363cfa8d58ae3f2b2700ad7
But presumably you’re referring to something else, right?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-13 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 12:40 Reproducible Research Hackathon: Friday, July 3rd simon tournier
2020-07-01 4:57 ` Pjotr Prins
2020-07-01 9:10 ` zimoun
2020-07-01 9:21 ` Efraim Flashner
2020-07-03 17:10 ` zimoun
2020-07-03 17:36 ` Ricardo Wurmus
2020-07-03 17:56 ` Paul Garlick
2020-07-03 18:19 ` zimoun
2020-07-07 17:52 ` Paul Garlick
2020-07-03 21:17 ` Ricardo Wurmus
2020-07-07 17:44 ` Paul Garlick
2020-07-04 9:51 ` Konrad Hinsen
2020-07-13 13:41 ` Ludovic Courtès [this message]
2020-07-14 8:13 ` Konrad Hinsen
2020-07-14 8:54 ` Bonface M. K.
2020-07-14 19:53 ` Konrad Hinsen
2020-07-14 13:18 ` Ludovic Courtès
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=875zarr0pk.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=simon.tournier@univ-paris-diderot.fr \
/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).