[BusyBox] Compiling busybox aginst uClilbc

[Erik Andersen]

On Tue Jan 16, 2001 at 02:44:16PM -0600, Richard A. Smith wrote:
> I don't seem to be able to compile busybox vs uClibc.  
[------snip------]
> Do I have to do anything else?

First, be sure the library is compiled and set up correctly.
This is what I do

    andersen at sage:~/CVS/uClibc$ cvs up
    andersen at sage:~/CVS/uClibc$ cp Config.x86 Config
    andersen at sage:~/CVS/uClibc$ make
    <stuff compiles>
    andersen at sage:~/CVS/uClibc$ sudo cp libuClibc.so.1 /lib
    andersen at sage:~/CVS/uClibc$ sudo ln -fs /lib/libuClibc.so.1 /lib/libuClibc.so
    andersen at sage:~/CVS/uClibc$ sudo ldconfig
    cd ~/andersen at sage:~/CVS/uClibc$ cd ~/CVS/busybox


Then in the busybox makefile you need something like this:

    LIBCDIR=/home/andersen/CVS/uClibc
    LDFLAGS+=-nostdlib
    LIBRARIES = -luClibc -lgcc $(LIBCDIR)/crt0.o
    CROSS_CFLAGS+=-nostdinc -I$(LIBCDIR)/include -I$(GCCINCDIR)
    GCCINCDIR = $(shell gcc -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp")

Note that LIBCDIR uses the full path -- make doesn't do ~ expansion...

> Oh and BTW... Who ever is doing documentation might add somewhere that when building a boot 
> system using busybox the link to init must be a HARD link.  A softlink does not work.  By 
> default the make install creates symbolic links.  

Really?  I know I've used symlinks before...  
What type of filesystem for root?

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--