Þann Laugardagur 10. september 2005 05:19 skrifaði Hamish Moffatt:
> On Fri, Sep 09, 2005 at 10:28:41PM +0200, Gudjon I. Gudjonsson wrote:
> > Unfortunately I do still have a problem with chroot when I run
> > cadence.
> >
> > When I do in chroot /var/chroot/sarge-amd64
> > [EMAIL PROTECTED]:~$ strace /usr/local/cadence/tools/bin/cds_root
> > execve("/usr/local/cadence/tools/bin/cds_root",
> > ["/usr/local/cadence/tools/bin/cds_root"], [/* 43 vars */]) = 0
> > strace: exec: No such file or directory
>
> [..]
>
> > This is in fact normal behaviour but there seems to be no difference
> > between these files in / and /var/chroot/sarge-amd64. What makes files
> > sometimes unexecutable?
>
> Is it a binary or a script? If it's a script, a missing interpreter will
> cause the problem you describe. Missing linker (ld.so) might also.
>
> Hamish
> --
> Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Thanks for the help.
It is an executable file that is run by another script and the script runs
in chroot so that is no problem. The script is supposed to set up
LD_LIBRARY_PATH so the cds_root should be able to run on its own. I had a
similar problem when trying to run BlackAdder on Debian some months ago but
unfortunately I didn't report that. The files where there but unable to run.
Regards
Gudjon
