I agree on this. On the other hand, I seem to remember that any program using the glibc's network name resolver can be totally statically linked in Linux.
That has probably something to do with those dynamic /lib/libnss* modules for name resolution, specified in /etc/nsswitch.conf. Maybe a special compilation of glibc with those modules in static form can produce static binaries, but I don't think any distribution comes with a precompiled glibc like that. 2008/1/3, Martin Neubauer <[EMAIL PROTECTED]>: > For one, I think opera-static doesn't mean it's a static binary but qt is > linked in statically. On the other hand, until just a couple years ago > static linking in linux was no problem at all. But around the time linux 2.6 > came out, the glibc guys apparently decided nobody used static linking > anyway and merrily bollocksed it up. Great, now I'm depressed. > > * Federico G. Benavento ([EMAIL PROTECTED]) wrote: > > hola, > > > > getting real static binaries in linux is a bit tricky and no one seems to > > be doing so, they always need ld-linux.so, libnss and others. > > cinap creates some kind of bundles that create a fake ns in /tmp/$lbun > > with this (http://9hal.ath.cx/usr/cinap_lenrek/lbun/mklbun) or something > > like, but I know he got opera running in Plan 9. > > http://9hal.ath.cx/usr/cinap_lenrek/plan9opera.png >
