[uClibc] uclibc-gcc using wrong libraries when compiling?

[Scott Stickeler]

Problem solved. Actually it was not really a problem at all. 

First, being new to the gnu toolchain, I didn't know about the strip option.
This makes a big difference :). 

Second, the reason that the binaries compiled with uclibc and glibc were exactly
the same size is that I never actually compiled anything with glibc. 

There are symbolic links in the toolchain bin directory that map
powerpc-linux-xxxx to the appropriate uclibc files. Since this bin directory
was one of the first directories in my path, when I ran powerpc-linux-gcc it
was still using the uclibc executable not the powerpc-linux-gcc I had compiled
for glibc, hence the exact same file sizes.

Thanks for the responses.

-Scott

Quoting Scott Stickeler <scott at guy-smiley.com>:

> 
> > If you have everything included in uClibc this sounds about right. 
> > Locale support adds a lot to static programs.
> > 
> 
> The thing that makes me suspicious is that the files are exactly the same
> size
> as those compiled with glibc. 
> 
> > > The libraries paths seem weird. Is this the problem or am I missing
> > something?
> > 
> > gcc -v will show you what libraries are being pulled in.
> 
> Will this tell me the path to the libraries as well?
> 
> Thanks,
> Scott
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc
>