Ron Jones wrote:
# ls -l /bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /bin/bash
# ls -l /lib/libtermcap.so.2
lrwxrwxrwx 1 root root 19 Sep 29 2005 /lib/libtermcap.so.2 ->
libtermcap.so.2.0.8
# ls -l /lib/libdl.so.2
lrwxrwxrwx 1 root root 14 Mar 22 06:00 /lib/libdl.so.2 -> libdl-2.3.4.so
# ls -l /lib/tls/libc.so.6
lrwxrwxrwx 1 root root 13 Mar 22 06:00 /lib/tls/libc.so.6 -> libc-2.3.4.so
# ls -l /lib/ld-linux.so.2
lrwxrwxrwx 1 root root 11 Mar 22 06:00 /lib/ld-linux.so.2 -> ld-2.3.4.so
Now let's verify that they look the same in the sandbox:
# ls -l /opt/qmt-sandbox/bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /opt/qmt-sandbox/bin/bash
# ls -l /opt/qmt-sandbox/lib/libtermcap.so.2
lrwxrwxrwx 1 root root 20 Aug 20 12:18 /opt/qmt-sandbox/lib/libtermcap.so.2
-> libtermcap.so.2.0.8
# ls -l /opt/qmt-sandbox/lib/libdl.so.2
lrwxrwxrwx 1 root root 15 Aug 20 12:17 /opt/qmt-sandbox/lib/libdl.so.2 ->
libdl-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/tls/libc.so.6
lrwxrwxrwx 1 root root 14 Aug 20 12:17 /opt/qmt-sandbox/lib/tls/libc.so.6
-> libc-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/ld-linux.so.2
lrwxrwxrwx 1 root root 12 Aug 20 12:18 /opt/qmt-sandbox/lib/ld-linux.so.2
-> ld-2.3.4.so
Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work,
and give you a bash prompt.
[EMAIL PROTECTED] bin]# chroot /opt/qmt-sandbox/
Chroot: cannot run command '/bin/bash' : No such file or directory
Please do these commands on your machine and post the results. I'm thinking
at this point that
64-bit might have something to do with it, but that's just a guess since
it's the only thing I see
that's different (so far).
See results of commands (above) shown below the commands themselves
Ron
Man, this error is subtle. There's a bug in the script that causes bash64 to
include a space in front of the link target names (notice "-> ld-2.3.4.so).
Much easier to notice when doing ls -l while logged on to your machine -
invalid symlinks are bold red. For whatever reason, bash32 interprets the
leading space as being outside of the variable name when it's not quoted, so
it 'worked', but it wasn't quite right.
I've got a fix for you to try. I'm confident that this will at least fix
this bug.
Edit qmt-newmodel.sh, changing line 783 from
target=${ls#*->}
to
target=${ls#*-> }
IOW, add a space after the '>', and the leading space will be removed from
$target.
Then rerun the script, rebuilding the sandbox. While the sandbox is
building, you can 'ls -l /opt/qmt-sandbox/lib' after that directory is
built, and you should see no more broken links (bold red).
Let me know how you make out.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
