<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV></DIV>
<DIV>Ken, Joe,</DIV>
<DIV> </DIV>
<DIV>Good news: hello world program compiled with CLFS cross compiler runs on one of the targets that has a 2.6 kernel installed.</DIV>
<DIV> </DIV>
<DIV>It will only run when compiled with the -static switch to gcc, and it's 2.5M in size:</DIV>
<DIV> </DIV>
<DIV>
<DIV> <A href="mailto:v4@v4-130"><FONT color=#0000ff>v4@v4-130</FONT></A>: [~]#ls -al<BR>drwx------ 2 v4 users 1024 Jul 9 14:33 .<BR>drwxr-xr-x 3 root root 1024 May 22 16:55 ..<BR>-rw------- 1 v4 users 88 Jul 9 14:26 .bash_history<BR>-rwxr-xr-x 1 v4 users 2600205 Jul 10 2008 hello<BR>-rwxr-xr-x 1 v4 users 3022 Jul 10 2008 helloworld<BR>-rwxr-xr-x 1 v4 users 12143 Jul 10
2008 hw</DIV>
<DIV> </DIV>
<DIV>hello is linked with -static:</DIV></DIV>
<DIV><A href="mailto:v4@v4-130">v4@v4-130</A> [~]# ./hello<BR>Hello world</DIV>
<DIV> </DIV>
<DIV>hw is linked without -static:<BR><A href="mailto:v4@v4-130">v4@v4-130</A> [~]# ./hw<BR>-bash: ./hw: No such file or directory</DIV>
<DIV> </DIV>
<DIV>libc.so.6 is a link:</DIV>
<DIV><A href="mailto:v4@v4-130">v4@v4-130</A> [v4]# ls -l /opt/ppc/powerpc-linux/lib/libc.so.6<BR>lrwxrwxrwx 1 root root 13 May 22 16:55 /opt/ppc/powerpc-linux/lib/libc.so.6 -> libc-2.2.5.so<BR></DIV>
<DIV>libc-2.2.5.so will not run (I was trying to see it's version at cmd line):</DIV>
<DIV><A href="mailto:v4@v4-130">v4@v4-130</A> [v4]# /opt/ppc/powerpc-linux/lib/libc-2.2.5.so<BR>bash: /opt/ppc/powerpc-linux/lib/libc-2.2.5.so: No such file or directory<BR></DIV>
<DIV>This behavior of library functions emitting this "No such file or directory" print statement is so wierd. I'm just a little over my head when delving into glibc: I've written applications on linux/unix/xenix systems since the mid 80's, and embedded systems since the late 80's, but never learned the nuances of linux/glibc/gcc, but I'm learning, no small thanks to CLFS.</DIV>
<DIV> </DIV>
<DIV>My next step is to try to compile passwd. Anyway, thanks for your help. I'm certainly encouraged that the cross compiler built executable will run on the target. If there's anything obvious here please let me know.</DIV>
<DIV> </DIV>
<DIV>Regards, Anthony.</DIV>
<DIV><BR> </DIV></div></body></html>