Am Donnerstag, 3. Januar 2013 schrieb Ludovic Courtès:

> Andreas Enge <andreas@enge.fr> skribis:

> > So should this be checked by ./configure?

> It wouldn’t be enough: nscd could be running at configure time, and not

> later.

 

True, but it would be better than nothing - as long as it is not packaged for distributions, the code will most probably run on the machine where it has been compiled.

 

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

 

> Can you try:

> strace -o ,,s

> /nix/store/7ys18z66aih9dwzlwkj2jynk05a3xsds-guile-bootstrap-2.0/bin/gui

> le -c '(pk (getaddrinfo "ftp.gnu.org" "80" AI_NUMERICSERV))' grep nscd

> ,,s

> The above path is that of the bootstrap Guile in master.

 

The same problem:

privat@debian:/tmp$ strace -o ,,s /nix/store/7ys18z66aih9dwzlwkj2jynk05a3xsds-guile-bootstrap-2.0/bin/guile -c '(pk (getaddrinfo "ftp.gnu.org" "80" AI_NUMERICSERV))'

 

;;; ((#(1024 2 1 6 #(2 3497454356 80) #f) #(1024 2 2 17 #(2 3497454356 80) #f) #(1024 2 3 0 #(2 3497454356 80) #f) #(1024 10 1 6 #(10 42541952298791455573290623124440612875 80 0 0) #f) #(1024 10 2 17 #(10 42541952298791455573290623124440612875 80 0 0) #f) #(1024 10 3 0 #(10 42541952298791455573290623124440612875 80 0 0) #f)))

 

privat@debian:/tmp$ grep nscd ,,s

connect(5, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)

connect(5, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)

 

Admittedly, I recently downloaded new tarballs mainly for my own new packages, and since I needed the hash, I did so using guix-download. So maybe it does not work any more since guix includes the build code from nix? It definitely did work at some point in time for my first "hello".

 

Andreas