[uClibc]Setting up development environment on target system
Nick Jennings
nkj at namodn.com
Thu Dec 5 22:45:02 UTC 2002
Just to follow up on my own thread (for the archives). The problem I had
was that doing another 'make' didn't recompile everything. I had to
'make clean' first. (mentioned in the INSTALL file).
- Nick Jennings
On Wed, Dec 04, 2002 at 03:04:07PM -0800, Nick Jennings wrote:
> Hello,
>
> I've got an old 486 laptop w/4mb of RAM that I managed to get running
> with busybox compiled against uClibc.
>
> So far all of the compilation has been done on my build system, and then
> copied over to my 486. Now I'd like to be able to compile stuff on my
> laptop directly.
>
> I tried copying over the uClibc development environment, but I noticed,
> the devel binaries are dynamically linked to glibc libaries. Understandable,
> so I re-built the uClibc stuff with the uClibc dev environment on my
> PATH. Hoping it would link against the uClibc libraries, and therefore
> run on my 486. No luck...
>
> # ldd <PREFIX>/usr/i386-linux-uclibc/usr/bin/gcc
> libc.so.6 => /lib/libc.so.6
> ld-linux.so.2 => /lib/ld-linux.so.2
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2
>
>
> When these directories are copied onto my 486, they do not run. So how do
> I get my development environment properly bootstrapped onto my 486? I'd
> like to not be so dependant on getting my main system for compilation.
>
> Any info will help, as I am new to this area of system libraries and stuff.
>
> - Nick
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc
>
More information about the uClibc
mailing list