unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Guillaume Le Vaillant <glv@posteo.net>,
	Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 56353@debbugs.gnu.org, xiewensheng@hotmail.com
Subject: bug#56353: sbcl-2.2.6 build fail
Date: Sat, 02 Jul 2022 17:49:48 +0100	[thread overview]
Message-ID: <87ilof78y0.fsf@cbaines.net> (raw)
In-Reply-To: <6B9D52CF-992E-402B-9ABA-4E017804B4A6@tobias.gr>

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


Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

> On 2 July 2022 09:29:22 UTC, Wensheng Xie <xiewensheng@hotmail.com> wrote:
>>Das Erstellungsprotokoll kann unter „/var/log/guix/drvs/6l/q7dfdfzrlp24lmhj95fcnvkr2mrqfz-sbcl-2.2.6.drv.bz2“ eingesehen werden.
>
>
> This log file is always a good idea to include.

I think this is the equivalent non-grafted derivation:

  https://data.guix.gnu.org/gnu/store/m7xw777v5agldb76gbqkqdvrrlj5d7zy-sbcl-2.2.6.drv

There are plenty of failed builds on bordeaux.guix.gnu.org. I managed to
get it to build successfully once though on my laptop.

Guillaume, any ideas if sbcl@2.2.6 is just really unlikely to build
successfully, or if there's particular conditions for it to build?

Thanks,

Chris

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

  reply	other threads:[~2022-07-02 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02  9:29 bug#56353: sbcl-2.2.6 build fail Wensheng Xie
2022-07-02 11:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-07-02 16:49   ` Christopher Baines [this message]
2022-07-02 17:08     ` Guillaume Le Vaillant
2022-07-02 19:26       ` Christopher Baines
2022-07-03  8:33         ` bokr
2022-07-03  8:51           ` Guillaume Le Vaillant
2022-07-03 10:09             ` Guillaume Le Vaillant

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=87ilof78y0.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=56353@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=me@tobias.gr \
    --cc=xiewensheng@hotmail.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).