[uClibc]Anyone found the cause...

[Erik Andersen]

On Wed Jan 08, 2003 at 02:41:16PM -0500, Thomas Cameron wrote:
> Erik,
> 	I am currently _completely_ erasing my test buildroot directory, and checking 
> out a new copy from the cvs archive at uclibc.org.  I assume this is the 
> proper one to use, as I do not know of any other besides the possibility of 
> their being an copy for TuxScreen.
> 
> 	Out of curiosity, what is the configuration you are building buildroot with?  
> Any special settings, or do you build it exactly as it comes from the CVS 
> repository?  Just curious.

Using stock buildroot.  Do a 'cvs up' to be completely in sync.
At this point, the only difference vs stock I have is the
following in the toplevel Makefile.

     # Openssh...
    -#TARGETS+=zlib openssl openssh
    +TARGETS+=zlib openssl openssh
     
     # Everything needed to build a full uClibc development system!
    -#TARGETS+=coreutils findutils bash make sed gawk gcc_target
    +TARGETS+=coreutils findutils bash make sed gawk gcc_target
     
     # Of course, if you are installing a development system, you
     # may want some header files so you can compile stuff....
    -#TARGETS+=ncurses-headers zlib-headers openssl-headers
    +TARGETS+=ncurses-headers zlib-headers openssl-headers
     
     # Some nice debugging tools
    -#TARGETS+=gdb strace
    +TARGETS+=gdb strace
     
     # The Valgrind debugger
    -#TARGETS+=valgrind
    +TARGETS+=valgrind

I'm going to rebuild the _whole_ thing once again, just to
be sure, but thus far at least, it works for me.  Starting
build now.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--