all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Charles via Guix-patches via <guix-patches@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 50838@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: [bug#50838] Update sbcl
Date: Mon, 27 Sep 2021 19:45:39 +0000	[thread overview]
Message-ID: <6MX54YemJ-AGcuLSj62jQBOdU2WxXszXgHBDPRulsoX2FoxzEbRYkUh51n6r7uj-8UIGHqi_btoQ6NOiRamWkM0zevhOLA36pvM3-s7-PRU=@protonmail.com> (raw)
In-Reply-To: <87tui6gpay.fsf@kitej>

I built all sbcl-* packages, I used this snippet to build them; let me know if there is a better way.

./pre-inst-env guix build $(./pre-inst-env guix search "^name: sbcl-" | awk '{ print $2 }' | tr '\n' ' ')

sbcl-burgled-batteries3 fails to build. It also fails on sbcl 2.1.6. Perhaps people are not really using the sbcl version of this package and just using the ecl version as it builds fine. I'm not sure how the build system works for cl- packages, but apparently it uses sbcl too.

Same story with sbcl-png.

These are the only two offenders; all other packages built fine.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, September 27th, 2021 at 7:32 AM, Guillaume Le Vaillant <glv@posteo.net> wrote:

> Hi,
>
> Some time ago when Pierre Neidhardt tried to update SBCL to 2.1.7, some
>
> packages failed to compile (because of changes in the internals of SBCL
>
> I think). See commits b07581d6e24bf5fa4676bcebaba75315bbbb01e6 and
>
> 7c6ace67bb8ef421965e3f1cc1a02caf54c813f5.
>
> Did you try building all the sbcl-* packages with SBCL 2.1.8 to check if
>
> everything works fine?
>
> If some packages are failing, we will have to update them as well
>
> (upstreams probably have commits or PRs to fix compatibility with newer
>
> SBCL versions).




  reply	other threads:[~2021-09-27 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  5:51 [bug#50838] Update sbcl Charles via Guix-patches via
2021-09-27 12:32 ` Guillaume Le Vaillant
2021-09-27 19:45   ` Charles via Guix-patches via [this message]
2021-09-28  1:54     ` Charles via Guix-patches via
2021-09-28  9:47       ` bug#50838: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='6MX54YemJ-AGcuLSj62jQBOdU2WxXszXgHBDPRulsoX2FoxzEbRYkUh51n6r7uj-8UIGHqi_btoQ6NOiRamWkM0zevhOLA36pvM3-s7-PRU=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=50838@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    --cc=glv@posteo.net \
    --cc=mail@ambrevar.xyz \
    /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.