[lsb-discuss] Getting started with LSB Sample Implementation environment
dyek at real.com
Fri Mar 2 14:24:21 PST 2007
At 01:22 PM 3/2/2007, Stew Benedict wrote:
>I haven't really used the SI before, but probably a good time for me to
>try. I set it up basically the same as you, although on an x86_64 host:
>alias chrootSI='linux32 sudo /usr/local/bin/chroot /mnt/LSB/lsbsi-core-ia32'
>Compiled a hello.c both with lsbcc and gcc on a SLES10 ia32 chroot.
>The lsbcc compiled "hello" runs in the SI, while the gcc compiled one does
>not, likely due to the lack of /lib/ld-linux.so.
>It looked like your original compile in the build environment was with
>gcc, not lsbcc?
>Hope this helps.
I started with LSB chroot Build Environment and sticked to it, without
trying out lsbcc. I think I'll try it out, since our build team is planning
to use lsbcc, instead of BE.
So, I attempted to fix the BE by renaming the dynamic linker to ld-lsb.so.3:
bash-3.1$ ls -l /lib/ld*
lrwxrwxrwx 1 root root 11 Mar 2 14:01 /lib/ld-2.4.so -> ld-lsb.so.3
-rwxr-xr-x 1 root root 600770 Mar 2 13:59 /lib/ld-2.4.so.orig
lrwxrwxrwx 1 root root 11 Mar 2 14:02 /lib/ld-linux.so.2 -> ld-lsb.so.3
-rwxr-xr-x 1 root root 600770 Jul 15 2006 /lib/ld-lsb.so.3
Apparently, that didn't work:
bash-3.1$ ./lsbappchk helloworld
Checking binary helloworld
Incorrect program interpreter: /lib/ld-linux.so.2
Header[ 1] PT_INTERP Failed
Found wrong intepreter in .interp section: /lib/ld-linux.so.2 instead of:
I don't know how the linker decides which dynamic linker to specify...got
to dig for information.
More information about the lsb-discuss