From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Core-updates: Downloads do not work
Date: Mon, 07 Jan 2013 23:17:25 +0100 [thread overview]
Message-ID: <87pq1gwscq.fsf@gnu.org> (raw)
In-Reply-To: <201301072245.53296.andreas@enge.fr> (Andreas Enge's message of "Mon, 7 Jan 2013 22:45:52 +0100")
Hi Andreas!
Andreas Enge <andreas@enge.fr> skribis:
> After updating, things still do not work, which makes sense, since the new
> bootstrap binaries are not yet downloaded:
Ah, you need to:
$ rm distro/packages/bootstrap/x86_64-linux/guile-*.tar.xz
$ make
The latter will download the current guile-2.0.7.tar.xz bootstrap
binary, and check its hash (the hash of that tarball is only checked
upon downloading, by build-aux/download.scm.)
> However, I can execute
> guix-download http://www.fdn.fr/~lcourtes/software/guix/packages/x86_64-
> linux/20130105/gcc-4.7.2.tar.xz
> (as well as for all other packages), and then start a build.
>
> How come that "guix-download" does work, but the same download fails
> through "guix-build"?
That’s because guix-download uses your Guile, which is a full-fledged
Guile linked against a feature-complete libc, whereas the old bootstrap
Guile was statically linked against a libc whose getaddrinfo depended on
a running nscd to work.
Does that clarify a bit? :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-01-07 22:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 8:55 Core-updates: Downloads do not work Andreas Enge
2013-01-03 15:01 ` Ludovic Courtès
2013-01-03 15:28 ` Andreas Enge
2013-01-03 16:05 ` Ludovic Courtès
2013-01-03 16:45 ` Andreas Enge
2013-01-03 20:53 ` Ludovic Courtès
2013-01-04 15:57 ` Andreas Enge
2013-01-04 17:17 ` Ludovic Courtès
2013-01-06 0:20 ` Ludovic Courtès
2013-01-07 21:45 ` Andreas Enge
2013-01-07 22:17 ` Ludovic Courtès [this message]
2013-01-08 8:54 ` Andreas Enge
2013-01-08 22:51 ` Ludovic Courtès
2013-01-09 6:25 ` Andreas Enge
2013-01-09 13:51 ` Ludovic Courtès
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=87pq1gwscq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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).