Hi Everyone.

So I'm an embedded linux developer. I'm starting out with a new 2.6 based kernel. I'm able to use the GNU cLib and I create a ramdisk. I also use busybox and tinylogin.

So usually at first what I do is create a ramdisk_source directory which contains basically my linux root directory, you know.. /etc /bin /sbin ...

I don't have any inittab or anything like that yet.

I run and I get the error...
libm.so.6 is in my /lib directory.

My Question

Where or when in the bootup process do I need to set my LIB path? Or do I need to? Do I need an inittab? If so, what is the LIB path variable I need to set?

Thanks.

I'm still a and I think I will be FOREVER!

Is the library in the /lib of the ramdisk? Such is essential for chrooting. I would assume you have done so, but it must be there.

Yep. But I think I just found the problem. When I did

ldd $CHROOTHOME/bin/sh I found a wayward lib reference in there. So it was to /lib/tls/libc.....

So that definately isn't in my path! UGH!

This Linux stuff ..

Its a love hate relationship I think.

So yes the problem was when I did a ldd on my applets (i.e. /bin/sh, /bin/cat... whatever... ) I had a bad lib linked in there. THEN!!!!
I did an ldd on the libs as well because I kept getting the same error message. I found out that the libs weren't build correctly. What a chore.

Ok..what I was trying to do.

Trying to build my own "linux" from scratch with a GNU toolchain.

Problem I had....

Was that when I built the GNU libc, I didn't have the same directory structure as my "chroot" jail. Therefore all the lib paths were off.

So .. short story longer...

Make your toolchain and your system you are running on the same.

-netstv