From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Bengt Richter <bokr@bokr.com>
Cc: 37549@debbugs.gnu.org
Subject: bug#37549: guix build bootstrap-tarballs installed but strip-install failed
Date: Sun, 29 Sep 2019 11:05:59 +0200 [thread overview]
Message-ID: <878sq74glk.fsf@gnu.org> (raw)
In-Reply-To: <20190929070712.GA127225@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Sun, 29 Sep 2019 00:07:12 -0700")
Bengt Richter writes:
> I tried
> guix build bootstrap-tarballs
Yes, sadly that's not supported on current master. It should work on
core-updates. So I tried that and found it fails in similar ways.
> ERROR: In procedure lstat:
> In procedure lstat: No such file or directory: "/gnu/store/xjbkz6645qccnvfkmbc4wsvh7lffg2jn-mes-minimal-0.20/share/mes/scaffold"
> builder for `/gnu/store/w8y538fhxr9d9sm6653jq5xsl89q0aqk-mes-minimal-0.20.drv' failed with exit code 1
> build of /gnu/store/w8y538fhxr9d9sm6653jq5xsl89q0aqk-mes-minimal-0.20.drv failed
Ah, that's not good. The new Reduced Binary Seed bootstrap must use Mes
0.19. Building the new bootstrap binaries is -- apparently -- only
works on tag bootstrap-20190815.
> HTH in some way.
Yes, thank you; I'm looking into it. Mes should be fixed on 0.19,
MesCC-Tools schould be fixed on 0.5.2 and I just found that building
bootstrap-bash also breaks due to an update to bash-5.
Greetings,
jannneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2019-09-29 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 7:07 bug#37549: guix build bootstrap-tarballs installed but strip-install failed Bengt Richter
2019-09-29 9:05 ` Jan Nieuwenhuizen [this message]
2019-09-29 11:33 ` Jan Nieuwenhuizen
2019-09-29 16:13 ` Jan Nieuwenhuizen
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=878sq74glk.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=37549@debbugs.gnu.org \
--cc=bokr@bokr.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 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).