unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 41481@debbugs.gnu.org
Subject: bug#41481: Can't build glibc-mesboot0
Date: Sat, 23 May 2020 16:19:09 +0200	[thread overview]
Message-ID: <bab1951d56f028afbdc23d928aa401c3c9fb330a.camel@gnu.org> (raw)
In-Reply-To: <87zh9yixqr.fsf@gnu.org>

Hi Mathieu,

Thanks for the fast response!

On Sat, 2020-05-23 at 15:31 +0200, Mathieu Othacehe wrote:
> 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.

Right, so this will fix itself once I can do a 'guix pull'.

> > 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?

No, but it is on an SSD (Samsung EVO 850), and there are two NVME
drives in the system, but these are not mounted.  So I think I should
dodge that bug.

Is there a substitute available for glibc-mesboot0?

Kind regards,
Roel Janssen






  reply	other threads:[~2020-05-23 14:20 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
2020-05-23 14:19   ` Roel Janssen [this message]
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=bab1951d56f028afbdc23d928aa401c3c9fb330a.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=41481@debbugs.gnu.org \
    --cc=othacehe@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).