[uClibc]Uclibc libraries...

[Tom Cameron]

Erik,
	Thanks!  I didn't even look that far down in Config...simply because
traditionally, it hasn't been set.  I haven't really looked @ the scripts
because I use my own to generate things..you know us geeks..our way is the
best...right?  ; )  I apologize for making such a foolish mistake.

--
Thomas Cameron
Network Technician / Operations Specialist
St. Mary's Bank

> -----Original Message-----
> From:	Erik Andersen [SMTP:andersen at lineo.com]
> Sent:	Monday, May 07, 2001 10:53 AM
> To:	Tom Cameron
> Cc:	'uclibc at uclibc.org'; busybox at uclibc.org
> Subject:	Re: [uClibc]Uclibc libraries...
> 
> On Mon May 07, 2001 at 09:24:29AM -0400, Tom Cameron wrote:
> > Hello all,
> > 	I just recently grabbed the latest CVS of uClibc, and compiled
> > everything against it (tinylogin, BusyBox, etc.).  But when I tried to
> > install it all on my target system, I noticed that uClibc installs to
> > /usr/i386-blah-blah-blah/*.  I looked in the Makefile, but didn't notice
> > anything that would install JUST the libraries in a specified path (I
> > already had to specify my development path).  Additionally, it installed
> a
> > TON of other stuff (the compiler, etc.).  My question is, HOW IN THE
> WORLD
> > DO I MAKE IT INSTALL _LIBRARIES_ TO MY /{development_path}/lib ?!?!  For
> now
> > I have made a TON of symlinks...but I do NOT want to use that as a final
> > solution.  As a foot note...I don't mind placing these libraries in my
> main
> > system's /lib directory, as long as they don't conflict with anything
> > already in there.
> 
> For a simple example of how to do this, Mark Whitley recently checked a
> bootfloppy directory into busybox, which we worked on to demo exactly how
> to
> make a bootable system.  It creates a shared uClibc + busybox boot floppy
> (in
> essence, it does what my ESC paper (that I can't release) did, but it does
> it
> automagically).  Anyways, since it automates the process you might want to
> take
> a look at what we did (or adapt the scripts for your own evil purposes).
> 
> As shown in the mkrootfs.sh script, to make uClibc install to /lib instead
> of
> the default /usr/i386-blah-blah-blah, you can either edit the
> uClibc/Config
> file and set INSTALL_DIR to nothing (i.e.  'INSTALL_DIR=') or you can
> specify
> it on the command line when you compile (i.e. 'cd uClibc; make
> INSTALL_DIR=').
> The default /usr/i386-blah-blah-blah simply makes it easier to develop
> things
> with uClibc on a host system.  Otherwise when compiling libfoo, if libfoo
> has a
> line like 'ld blah -o libfoo.so.9 -lc' when it links against libc ld will
> look
> in /lib for libc and now you have a broken libfoo.so.9 since it just
> linked vs
> glibc...
> 
>  -Erik
> 
> --
> Erik B. Andersen   email:  andersen at lineo.com
> --This message was written using 73% post-consumer electrons--