From: ludo@gnu.org (Ludovic Courtès)
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: 13958@debbugs.gnu.org
Subject: bug#13958: Failing net-db.test on armv5tel glibc 2.17
Date: Fri, 15 Mar 2013 14:48:37 +0100 [thread overview]
Message-ID: <87ppz0wz7u.fsf@gnu.org> (raw)
In-Reply-To: <20130315134040.GJ14560@vicerveza.homeunix.net> ("Lluís Batlle i Rossell"'s message of "Fri, 15 Mar 2013 14:40:40 +0100")
Lluís Batlle i Rossell <viric@viric.name> skribis:
> On Fri, Mar 15, 2013 at 02:36:40PM +0100, Ludovic Courtès wrote:
>> Lluís Batlle i Rossell <viric@viric.name> skribis:
[...]
>> > 16993 open("/nix/store/83fff5psdwad2vcy44lv5gwyzfmj4433-glibc-2.17/lib/libnss_myhostname.so.2", O_R
>> > DONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
>>
>> This is most likely the culprit. Presumably you forgot to add
>> libnss_myhostname to $LD_LIBRARY_PATH, no?
>>
>> Also, what does /etc/nsswitch.conf look like?
>
> The hosts line:
> hosts: files dns myhostname
OK. I wonder if adding a [NOTFOUND=...] clause could help.
> Ok, so the source of that bad-handled message is a NSS problem in nix builds
> without chroot.
Yes, it’s reading an NSS configuration that cannot be used.
> What should be the proper user program reaction to that EAI_AGAIN + errno?
Ideally Guile would propagate the errno value. But in your case it’s
ENOENT, so the error message would be like:
failed to resolve host name: No such file or directory
This is not really more helpful than:
failed to resolve host name: System error
(That’s part of the reason why exceptions were invented. :-))
To me, that example is an argument in favor of the status quo in
Guile—i.e., keeping EAI_SYSTEM handling as it is.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2013-03-15 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130310225811.GO14560@vicerveza.homeunix.net>
[not found] ` <87txoert3q.fsf@gnu.org>
2013-03-14 14:03 ` bug#13958: Failing net-db.test on armv5tel glibc 2.17 Lluís Batlle i Rossell
2013-03-15 11:14 ` Ludovic Courtès
2013-03-15 11:34 ` Lluís Batlle i Rossell
2013-03-15 13:36 ` Ludovic Courtès
2013-03-15 13:40 ` Lluís Batlle i Rossell
2013-03-15 13:48 ` Ludovic Courtès [this message]
2013-03-25 21:47 ` 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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppz0wz7u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=13958@debbugs.gnu.org \
--cc=viric@viric.name \
/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.
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).