unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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 18:45:43 +0200	[thread overview]
Message-ID: <87r1przfwo.fsf@yamatai> (raw)
In-Reply-To: <CAJ3okZ1UC3fXedXOkU=cwRQ6Tv_iy7xK3xUKtWbND2HBpaUwBA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]


zimoun <zimon.toutoune@gmail.com> skribis:

>> Removing this source file timestamp from compiled files would simplify
>> things. Maybe nothing really depends on it and it would be possible...
>
>Thanks for the explanation.

A developer of SBCL agrees that the timestamp should be removed [1], but
currently Slime has a function depending on it. I asked if this could
be fixed [2]. We'll see...

[1] https://sourceforge.net/p/sbcl/mailman/message/37133640/
[2] https://github.com/slime/slime/issues/583

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-10-21 16:46 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 [this message]
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=87r1przfwo.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).