all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 46844@debbugs.gnu.org
Subject: bug#46844: guile2.2-bytestructures fails to  compile.
Date: Mon, 01 Mar 2021 09:06:49 +0100	[thread overview]
Message-ID: <3f495538d371826b84b9ec6864503c60844c1d95.camel@telenet.be> (raw)

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

Hi Guix,

guile2.2-bytestructures and guile2.0-bytestructures don't compile.
The reason seems to be that v1.0.9 uses (scheme eval), which isn't
defined in guile2.0 and guile2.2. v1.0.8 doesn't use (scheme eval)

Here's the commit that seems to introduce the issue while fixing
another:

guix time-machine --commit=0a1da4652d9bb93d530ca52710f30b5d05a4251d -- build guile2.0-bytestructures guile2.2-bytestructures

According to a "guix refresh --list-dependent guile2.0-bytestructures guile2.2-bytestructures"
on 372b15f8625e7f20cafdba2677d4bf3f5eccc127, only "guile2.0-git",
"guile2.2-parted" and "guile2.2-guix" depend on these packages,
so unless someone needs "guile2.2-guix", it should be safe to remove
these packages.

Greetings,
Maxime.

(This issue prevents creating an environment for https://issues.guix.gnu.org/46826)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

             reply	other threads:[~2021-03-01  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  8:06 Maxime Devos [this message]
2021-03-01 14:14 ` bug#46844: guile2.2-bytestructures fails to compile Ludovic Courtès
2021-03-01 14:47 ` Taylan Kammer
2021-03-03 14:56   ` Taylan Kammer
2021-03-05 15:36     ` Maxime Devos
2021-03-10 19:10 ` Taylan Kammer
2021-03-10 20:12   ` zimoun
2021-03-10 20:55     ` Taylan Kammer
2021-03-10 21:11       ` Taylan Kammer
2021-03-10 21:44         ` 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=3f495538d371826b84b9ec6864503c60844c1d95.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=46844@debbugs.gnu.org \
    /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.