all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: guix-devel@gnu.org
Subject: Unable to bootstrap Guix without substitutes
Date: Thu, 10 Feb 2022 16:33:37 -0500	[thread overview]
Message-ID: <CA+3U0ZkARzr=DRyysfxw=BPsy_WXT_kFQs-X_JoenE4xbA0v4Q@mail.gmail.com> (raw)

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

When installing the Guix binary distribution (both the 1.3.0 release and
most recent guix-binary on ci.guix.gnu.org) on a new system without
enabling substitutes the guix pull or install commands fail when building
bash-mesboot0.
  https://guix.gnu.org/manual/en/html_node/Binary-Installation.html

I see the same failure when building bash-mesboot0 on my working Guix
installation (with substitutes enabled, but disabled for this build):

--8<---------------cut here---------------start------------->8---
./pre-inst-env guix build --no-substitutes -e '(@@ (gnu packages
commencement) bash-mesboot0)'
--8<---------------cut here---------------end--------------->8---

The error from the log:

--8<---------------cut here---------------start------------->8---
checking whether #! works in shell scripts... Backtrace:
In ice-9/boot-9.scm:
 157: 14 [catch #t #<catch-closure c93c40> ...]
In unknown file:
   ?: 13 [apply-smob/1 #<catch-closure c93c40>]
In ice-9/boot-9.scm:
  63: 12 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 11 [eval # #]
In ice-9/boot-9.scm:
 793: 10 [call-with-input-file "./configure" ...]
In gash/gash.scm:
 121: 9 [#<procedure 12b0a80 at gash/gash.scm:120:19 (port)> #<input:
./configure 16>]
In gash/repl.scm:
  38: 8 [run-repl #<input: ./configure 16> #f]
In srfi/srfi-1.scm:
 619: 7 [for-each #<procedure eval-sh (exp)> (# # # # ...)]
In gash/shell.scm:
 277: 6 [sh:subshell #<procedure 146bf20 at gash/eval.scm:70:14 ()>]
 266: 5 [%subshell #<procedure 146bf20 at gash/eval.scm:70:14 ()>]
In ice-9/boot-9.scm:
 157: 4 [catch quit #<procedure 146bf20 at gash/eval.scm:70:14 ()> ...]
In srfi/srfi-1.scm:
 619: 3 [for-each #<procedure eval-sh (exp)> (# # #)]
In gash/shell.scm:
 241: 2 [#<procedure 162c5d0 at gash/shell.scm:235:17 ()>]
 165: 1 [sh:exec-let () "./conftest"]
In unknown file:
   ?: 0 [execle "./conftest" # "./conftest"]

ERROR: In procedure execle:
ERROR: In procedure execle: No such file or directory
yes
--8<---------------cut here---------------end--------------->8---

From the source's bash-2.05b/configure script, the failing section for
AC_SYS_INTERPRETER:

--8<---------------cut here---------------start------------->8---
echo "$as_me:11935: checking whether #! works in shell scripts" >&5
echo $ECHO_N "checking whether #! works in shell scripts... $ECHO_C" >&6
if test "${ac_cv_sys_interpreter+set}" = set; then
  echo $ECHO_N "(cached) $ECHO_C" >&6
else
  echo '#! /bin/cat
exit 69
' >conftest
chmod u+x conftest
(SHELL=/bin/sh; export SHELL; ./conftest >/dev/null)
if test $? -ne 69; then
   ac_cv_sys_interpreter=yes
else
   ac_cv_sys_interpreter=no
fi
rm -f conftest
fi
echo "$as_me:11952: result: $ac_cv_sys_interpreter" >&5
echo "${ECHO_T}$ac_cv_sys_interpreter" >&6
interpval=$ac_cv_sys_interpreter

if test $ac_cv_sys_interpreter = yes; then
cat >>confdefs.h <<\EOF
#define HAVE_HASH_BANG_EXEC 1
EOF

fi
--8<---------------cut here---------------end--------------->8---

The ci builds are marked successful, but the raw log file is either empty
or appears to substitute an earlier build.
  https://ci.guix.gnu.org/search?query=bash-mesboot0

Greg

[-- Attachment #2: Type: text/html, Size: 4164 bytes --]

             reply	other threads:[~2022-02-10 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 21:33 Greg Hogan [this message]
2022-02-11  1:39 ` Unable to bootstrap Guix without substitutes Timothy Sample
2022-02-14 21:38   ` Ludovic Courtès
2022-02-16 21:28   ` Greg Hogan
2022-02-17 15:18     ` Greg Hogan

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='CA+3U0ZkARzr=DRyysfxw=BPsy_WXT_kFQs-X_JoenE4xbA0v4Q@mail.gmail.com' \
    --to=code@greghogan.com \
    --cc=guix-devel@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.