From: Guillaume Le Vaillant <glv@posteo.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44112@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#44112: SBCL is not reproducible
Date: Wed, 21 Oct 2020 14:41:48 +0200 [thread overview]
Message-ID: <87wnzjzr77.fsf@yamatai> (raw)
In-Reply-To: <86o8kw80bl.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
zimoun <zimon.toutoune@gmail.com> skribis:
> Using Guix 58af4c9, the package ’sbcl’ seems not-reproducible.
>
> [...]
>
> I do not know if the patches in ’staging’ will fix this.
>
> Note that this issue does not imply that the build system
> ’asdf-build-system/sbcl’ is or will be not reproducible. However, this
> issues cuts any Diverse Double Compiling attempt.
IIRC, when compiling, SBCL puts the timestamp of the source file in the
compiled file. It's not a problem when just doing basic compilation
because the source files' timestamps have been set to "1970-01-01".
However, some packages generate some source files at build time, usually
containing things like data type sizes fetched from system header in
order to use C libraries with FFI. The timestamp of a generated file
is the current time, therefore the build is not reproducible.
IIRC, SBCL itself is built in 2 stages. First its core is compiled
using another Common Lisp implementation (currently clisp in Guix), then
the complete SBCL is compiled using the core compiled in stage 1. There
is probably also an embedded timestamp issue here (coming for clisp,
from SBCL, or both) causing the reproducibility issue.
The patches currently in the staging branch don't have any effect on
the generation of source files or on the format of the compiled files,
so they will not help with this issue.
Removing this source file timestamp from compiled files would simplify
things. Maybe nothing really depends on it and it would be possible...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-21 12:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zgcflzjn.fsf.ref@aol.com>
2020-10-21 8:12 ` bug#44112: SBCL is not reproducible zimoun
2020-10-21 12:41 ` Guillaume Le Vaillant [this message]
2020-10-21 13:37 ` zimoun
2020-10-21 13:43 ` zimoun
2020-10-21 14:32 ` Pierre Neidhardt
2020-10-21 15:13 ` zimoun
2020-10-21 16:45 ` Guillaume Le Vaillant
2020-10-21 16:55 ` Pierre Neidhardt
2020-10-22 11:19 ` zimoun
2020-10-22 12:13 ` Pierre Neidhardt
2020-10-21 14:32 ` Pierre Neidhardt
2021-01-19 16:48 ` zimoun
2021-01-23 9:19 ` Guillaume Le Vaillant
2022-11-25 17:22 ` bug#44112: Hendursaga via Bug reports for GNU Guix
2022-12-09 18:50 ` bug#44112: zimoun
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=87wnzjzr77.fsf@yamatai \
--to=glv@posteo.net \
--cc=44112@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--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).