monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] coLinux and 0.26pre1: Address family not supported


From: Matthew Gregan
Subject: Re: [Monotone-devel] coLinux and 0.26pre1: Address family not supported by protocol
Date: Thu, 19 Jan 2006 10:51:36 +1300
User-agent: Mutt/1.5.11

At 2006-01-18T18:21:30+0100, Henry Nestler wrote:

> after testing some variants, here is the final state.  :-(
> 
> mt026-semistatic.txt:
> Run as server on port 55555 don't work.
> 
> + monotone-0.26pre1-x86-semistatic --db=colinux-testing.db 
> --rcfile=serv_anonymous.lua serve --bind=monotone.colinux.org:55555 '*'
> monotone: network error: name resolution failure for monotone.colinux.org

Was the semistatic binary built on a modern machine, and you're not trying
to use it on an older machine?  If so, what probably happened is that
configure has detected getaddrinfo is available and has used it for name
resolution in the netxx code.  However, getaddrinfo doesn't work well with
statically linked binaries--in fact, the linker will warn you about this:

% cc -static getaddrinfo.c
/tmp/cclZTOsu.o: In function `main':
getaddrinfo.c:(.text+0x84): warning: Using 'getaddrinfo' in statically
linked applications requires at runtime the shared libraries from the glibc
version used for linking

...which means that the statically linked binary will work on the machine I
built it on, and any machine that happens to have a recent enough glibc, but
will fail with address resolution errors on machines with a glibc that is
too old.

> address@hidden mt-0.26]$ ./monotone-0.26pre1-x86-semistatic 
> --db=colinux-testing.db --rcfile=serv_anonymous.lua serve --bind=:55555 '*'
> monotone: fatal: std::runtime_error: network error: failure from socket(2): 
> Address family not supported by protocol
> monotone:
> monotone: this is almost certainly a bug in monotone.
> monotone: please send this error message, the output of 'monotone 
> --full-version',
> monotone: and a description of what you were doing to address@hidden
> monotone: discarding debug log (maybe you want --debug or --dump?)

This looks like a genuine bug.  It's probably something like us failing to
handle the fact that IPv6 is not available at runtime.  It'd be worth
opening a bug in the BTS about this.

Cheers,
-mjg
-- 
Matthew Gregan                     |/
                                  /|                address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]