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: Sun, 06 Jan 2013 01:20:55 +0100 [thread overview]
Message-ID: <87wqvrnouw.fsf@gnu.org> (raw)
In-Reply-To: <201301041657.17154.andreas@enge.fr> (Andreas Enge's message of "Fri, 4 Jan 2013 16:57:14 +0100")
Hi!
Andreas Enge <andreas@enge.fr> skribis:
> Am Donnerstag, 3. Januar 2013 schrieb Ludovic Courtès:
[...]
>> The C library’s getaddrinfo and other lookup functions can of course be
>> used without nscd, which is what your applications were using.
>>
>> What differs here is that the bootstrap Guile is statically linked, and
>> getaddrinfo and similar functions are not fully functional in statically
>> linked binaries.
>>
>> Hmm, that said, we should probably build the bootstrap libc with
>> --disable-nscd to avoid this problem altogether. I’ll try that, but
>> rebuilding everything is gonna take ages again...
>
> Well, if it solves the problem, it is worth the time!
I’ve rebuilt and uploaded all the bootstrap binaries with a libc that
doesn’t use the nscd and has static NSS modules. With commit 79580eb of
core-updates, these new binaries are being used.
Let me know how it works! :-)
Ludo’.
next prev parent reply other threads:[~2013-01-06 0:21 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 [this message]
2013-01-07 21:45 ` Andreas Enge
2013-01-07 22:17 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqvrnouw.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 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.