unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Debian package build problems with 2.0.9 (from git)
Date: Sat, 15 Jun 2013 16:28:59 -0500	[thread overview]
Message-ID: <87k3lvrrl0.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87a9mr3xv2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 15 Jun 2013 22:47:13 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> guile.info normally doesn’t need to be built when using the tarball.
> However, this wasn’t the case until a9ea4f909b9970c755b0a7c4cd9da907e66496fc.

Right.  I was asking about the case of building from git -- there I'm
using ./autogen.sh.  Is that not sufficient?

In any case, for now, the patch I posted handles the problem.

> (Where 2 is ENOENT.)
>
> Quoting http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13958#8 :
>
>   [T]here are only two occurrences of EAI_SYSTEM in inet/getaddrinfo.c
>   in glibc: one is for NETDB_INTERNAL, and the other is for
>   IDNA_DLOPEN_ERROR.
>
> Most likely, that means that one of the NSS modules specified in
> /etc/nsswitch.conf could not be loaded.

Here's the nsswitch.conf:

  passwd:         compat
  group:          compat
  shadow:         compat

  hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
  networks:       files

  protocols:      db files
  services:       db files
  ethers:         db files
  rpc:            db files

  netgroup:       nis

> Could you strace the C program above and check what happens?

  $ strace -f -p ./foo
  ...
  27725 open("/lib/libnss_mdns4.so.2", O_RDONLY|O_CLOEXEC) = 3
  27725 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\v\0\0\0\0\0\0"..., 832) = 832
  27725 fstat(3, {st_mode=S_IFREG|0644, st_size=10880, ...}) = 0
  27725 mmap(NULL, 2106096, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3717b7f000
  27725 mprotect(0x7f3717b81000, 2097152, PROT_NONE) = 0
  27725 mmap(0x7f3717d81000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f3717d81000
  27725 close(3)                          = 0
  27725 munmap(0x7f3718b48000, 203786)    = 0
  27725 open("/etc/mdns.allow", O_RDONLY) = -1 ENOENT (No such file or directory)
  27725 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
  27725 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3718b79000
  27725 write(1, "  err: -11\n", 11)      = 11
  27725 write(1, "errno: 2\n", 9)         = 9
  27725 exit_group(0)                     = ?

Hope this helps, and thanks.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  reply	other threads:[~2013-06-15 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 18:06 Debian package build problems with 2.0.9 (from git) Rob Browning
2013-06-15 20:47 ` Ludovic Courtès
2013-06-15 21:28   ` Rob Browning [this message]
2013-06-15 22:21     ` Ludovic Courtès
2013-06-16 15:18       ` Ludovic Courtès
2013-06-16  0:22 ` Daniel Hartwig
2013-06-16  4:52   ` Rob Browning

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=87k3lvrrl0.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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.
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).