[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] Problems gettings going with uclibc
From:       Erik Andersen <andersen () codepoet ! org>
Date:       2002-07-25 13:17:03
[Download RAW message or body]

On Thu Jul 25, 2002 at 07:34:27AM -0400, Joel Coltoff wrote:
> Hi,
> 
> I'm having some problems getting my system running with uclibc.
> My system runs fine with glibc. I'm running mipsel 2.4.18.
> 
> I hope I cover all the important details here.
>     The uclibc gcc is version 3.1. It was built using the stable
> 	release of uclibc (0.9.12).
>     The include files are the ones that come with uclibc and not
> 	the ones in the glibc toolchain.

ok

>     The build needed human intervention. After failing while trying
>         to make .../gcc-final/mipsel-linux/libiberty I poked through
> 	the config.log files and saw that it wanted to have ranlib
> 	run on .../build/gcc-final/gcc/libgcc.a. I did this and restarted
> 	the make.

I saw this problem before on mipsel before I made the latest
release of the toolchain, but I didn't spend the time to solve
it.  Any chance you could create a patch for the toolchain build
to fix the gcc Makefiles so they always run ranlib on libgcc.a? 

> This is what is happening. Busybox starts up and I can do some of the
> stuff you'd expect. I'm using the builtin ash as my shell. If I try to
> copy a file I get an error.
> 
>     freebird > cp hosts junk
>     cp: unable to stat `junk': (null)

Very odd.  busybox and uClibc work fine on my mipsel box
(2.4.19-rc1, Debian woody).  Where did you get your kernel
from?

 -Erik

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

[prev in list] [next in list] [prev in thread] [next in thread]