On Thu, Mar 12, 2009 at 03:05:17PM -0400, Neil Horman wrote:
quoted text
> On Thu, Mar 12, 2009 at 07:25:10PM +0100, Christer Weinigel wrote:
> > Neil Horman wrote:
> >> You don't need klibc, you can use regular glibc, and even build statically if
> >> you like.  You'll have to use dig or host to do name lookups, but thats also
> >> pretty easy to do.  This really is easier than you think it is :)
> >
> > Size, size, size.  The killer in the embedded world which rules out  
> > glibc.  And have you tried to link glibc statically with something that  
> > uses gethostbyname lately?  It is no longer possible since the  
> > introduction of all the introduction of the dynamic name lookup crap  
> > (ok, it's not really crap, I just feel like it's crap every time I try  
> > to link a networking application statically).  But that's a bit off  
> > topic since I don't need name lookups just to mount a NFS file system.  
> > uclibc also seems to have issues with networking and statically linked  
> > binaries, but I just haven't had time to figure out why yet.
> >
> 
> You didn't read what I wrote very closely, I specifically said you have to dig
> or host to do name lookups, specifically because of the issues with getXbyY.
> When I said I built busybox in 800k (400k compressed), That was with glibc
> statically linked.  End of story.  You're making up problems here, its not that
> big a deal.  I've not looked at the figures lately, but how much space does the
> dhcp client and nfs root code take up in the kernel these days?
 
just checked: disabling CONFIG_IP_PNP and CONFIG_IP_PNP_DHCP saves me
4456 bytes of zImage size on an ARM/PXA build

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html