From: Mathieu Othacehe <othacehe@gnu.org>
To: Roel Janssen <roel@gnu.org>
Cc: 41481@debbugs.gnu.org
Subject: bug#41481: Can't build glibc-mesboot0
Date: Sat, 23 May 2020 15:31:24 +0200 [thread overview]
Message-ID: <87zh9yixqr.fsf@gnu.org> (raw)
In-Reply-To: <4a8efd9bcc5ba77cb785d07347f29529b0bd2c5a.camel@gnu.org> (Roel Janssen's message of "Sat, 23 May 2020 15:10:14 +0200")
Hello Roel,
> I installed Guix System on my computer but I am facing two problems:
>
> 1. "guix pull" returns:
> Updating channel 'guix' from Git repository at '
> https://git.savannah.gnu.org/git/guix.git'...
> Building from these channels:
> guix https://git.savannah.gnu.org/git/guix.git 28e9a11
> guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found
>
> I worked around that by doing:
> $ find /gnu/store -name "glibc-bootstrap-system-2.2.5.patch"
> $ mkdir ~/dummy; cd ~/dummy; ln -s <the-location-of-this-file>
> $ export GUIX_PACKAGE_PATH=~/dummy
>
> Is there a proper way to fix this?
This has been fixed by 179e6c524ae4957e6ace83f72a5651767f786ca4. I guess
that if you pull again it should be fixed.
> 2. Installing emacs fails because the build of glibc-mesboot0 fails
> with:
>
> patch: **** Can't open patch file
> /gnu/store/wcz8d4vkcjs7c6m56mz3lsbkxgvnb17v-glibc-bootstrap-system-
> 2.2.5.patcherror 02:
> command "patch" "--force" "-p1" "-i"
> "/gnu/store/wcz8d4vkcjs7c6m56mz3lsbkxgvnb17v-glibc-bootstrap-system-
> 2.2.5.patch" failed with status 2
I don't know what forces a build of glibc-mesboot0, but this looks like:
https://lists.gnu.org/archive/html/bug-guix/2020-05/msg00335.html.
Is your store on an NVME disk, without encryption, by any chance?
Thanks,
Mathieu
next prev parent reply other threads:[~2020-05-23 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 13:10 bug#41481: Can't build glibc-mesboot0 Roel Janssen
2020-05-23 13:31 ` Mathieu Othacehe [this message]
2020-05-23 14:19 ` Roel Janssen
2020-05-23 14:39 ` Roel Janssen
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=87zh9yixqr.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=41481@debbugs.gnu.org \
--cc=roel@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).