On Sunday 21 September 2014 17:34:24 Michael Tokarev wrote: > This _is_ a glibc problem, and it can be trivially demonstrated by writing > a tiny program that calls, say, getaddrinfo() on its argument. When built > statically it always returns NOTFOUND, without any attempt to load any > nss modules or make dns queries or even do a /etc/hosts lookup. > > More, I don't think reassigning it to glibc will do any good either, because > static linking has been discoraged there for ages. Ok, thanks for the explanation. > I'm thinking about building busybox-static against uclibc. This means > compiling uclibc from uclibc-source during build time, but it is not much > more work than, say, compiling qemu (which also needs to link statically, > but has additional prob because it links with glib which can't be mixed > with uclibc). But anyway it will be a much bigger change than I'd like > to implement here. I understand your dilemma. Since this is outside my knowledge of expertise I can't asses the consequences of switching to a different glibc implementation nor offer a better idea. For my specific use case I can probably switch to the non-static version of busybox, although that doesn't resolve the issue reported here. I'd still be willing to test whatever solution you decide to implement. Cheers, Diederik -- GPG: 0x138E41915C7EFED6
Attachment:
signature.asc
Description: This is a digitally signed message part.