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: Sat, 23 Jan 2021 10:19:37 +0100 [thread overview]
Message-ID: <874kj8ko2e.fsf@yamatai> (raw)
In-Reply-To: <86r1mg98la.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
zimoun <zimon.toutoune@gmail.com> skribis:
> Hi,
>
> On Wed, 21 Oct 2020 at 14:41, Guillaume Le Vaillant <glv@posteo.net> wrote:
>> zimoun <zimon.toutoune@gmail.com> skribis:
>>
>>> Using Guix 58af4c9, the package ’sbcl’ seems not-reproducible.
>
> [...]
>
>> Removing this source file timestamp from compiled files would simplify
>> things. Maybe nothing really depends on it and it would be possible...
>
> Any news from upstream? Still unreproducible for me.
>
>
> All the best,
> simon
So far Slime still uses the function getting the source file timestamp,
so these timestamps can't be removed from SBCL.
A patch for Slime would be accepted (see [2]), but as far as I know
nobody has worked on it yet.
[2] https://github.com/slime/slime/issues/583
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-23 9:20 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kj8ko2e.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.