all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Unable to bootstrap Guix without substitutes
Date: Wed, 16 Feb 2022 16:28:13 -0500	[thread overview]
Message-ID: <CA+3U0Z=k=u=QU21v=MvHAhwSJ37mkjVdnLaHSRF3opkX_sqM8A@mail.gmail.com> (raw)
In-Reply-To: <875ypm9o72.fsf@ngyro.com>

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

On Thu, Feb 10, 2022 at 8:39 PM Timothy Sample <samplet@ngyro.com> wrote:

> I can perform the build successfully using
>
>     $ guix build --check \
>         -e '(@@ (gnu packages commencement) bash-masboot0)'
>
> That scary backtrace happens even for the successful build, so I’m
> pretty sure it is not the issue.  (Note that the configure test succeeds
> in the end with a “yes”.)
>
> Is there anything else suspicious in the logs?
>

Timothy,

Thank you for checking this on your own system, it was quite helpful to
know that the failure was not universal.

I found a solution to building bash-mesboot0 in bug #49985 in mounting /tmp
as tmpfs, as noted by Ludo'.

I then saw the error building binutils-mesboot0 as in bug #41264, for which
Mathieu proposed an idea for fixing Mes, still awaiting implementation.

As a temporary fix the same tmpfs trick works when bind mounting /gnu and
/var/guix onto the /tmp tmpfs. This should work for my workflow, and I am
glad to see that others have continued to attempt to bootstrap from source
without substitutes.

Greg

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

  parent reply	other threads:[~2022-02-16 21:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 21:33 Unable to bootstrap Guix without substitutes Greg Hogan
2022-02-11  1:39 ` Timothy Sample
2022-02-14 21:38   ` Ludovic Courtès
2022-02-16 21:28   ` Greg Hogan [this message]
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+3U0Z=k=u=QU21v=MvHAhwSJ37mkjVdnLaHSRF3opkX_sqM8A@mail.gmail.com' \
    --to=code@greghogan.com \
    --cc=guix-devel@gnu.org \
    --cc=samplet@ngyro.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 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.