unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 53157@debbugs.gnu.org
Subject: bug#53157: guix/ui.scm:203 requires guile-3.0.3
Date: Tue, 11 Jan 2022 11:14:13 +0100	[thread overview]
Message-ID: <871r1ey3yi.fsf@gnu.org> (raw)
In-Reply-To: <YdwalHGdP7UYnVyz@3900XT> (Efraim Flashner's message of "Mon, 10 Jan 2022 13:37:56 +0200")

Hi,

Efraim Flashner <efraim@flashner.co.il> skribis:

> I'm using ./pre-inst-env on my powerpc-linux machine, using guile-3.0.2
> as provided by Debian. When I try to run the following command:
> ./pre-inst-env guix build -L /path/to/repo -m /path/to/manifest.scm -n
> I get the following error:
>
> guix/ui.scm:230:13: error: default-optimization-level: unbound variable
>
> It doesn't make sense to gate this with (target-ppc32?) since it's due
> to the guile version. If I had configured within 'guix shell -D guix' I
> would be using guile-3.0.7.
>
> configure.ac checks for guile 3.0.

I’m in favor of updating ‘configure.ac’ to check for Guile > 3.0.x
(we’ll have to check which value of ‘x’ works).

But…

> (ins)efraim@g4:~$ apt-cache policy guile-3.0
> guile-3.0:
>   Installed: 3.0.2-2be32
>   Candidate: 3.0.2-2be32

… are you saying that requiring > 3.0.2 would cause problems when
porting to other architectures?

In general, we shouldn’t be tied to what Debian provides, but we can see
how much of a problem that would cause.  If it really is a problem, we
can adjust that one reference to ‘default-optimization-level’ in (guix
ui).

Thanks,
Ludo’.




  reply	other threads:[~2022-01-11 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 11:37 bug#53157: guix/ui.scm:203 requires guile-3.0.3 Efraim Flashner
2022-01-11 10:14 ` Ludovic Courtès [this message]
2022-01-25 22:58   ` Ludovic Courtès

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=871r1ey3yi.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53157@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 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).