Problem running lazarus programs
duncan-crosslfs at linuxowl.com
Fri Dec 9 08:23:31 PST 2005
Just wish to bump this question, I think that the problem is something
to do with the build of binutils as this gave more errors that it should
have done during the test phase. (maybe Ken can remember).
readelf shows quite a lot of information but I'm not sure where to look
in the output for signs of a problem.
On an LFS i386 6.1 system there are no problems running the lazarus
In case anybody wants to know lazarus is a Delphi like front end to the
> Hi all, don't know if you can help but I'm having a problem on an
> x86_64 (pure64) system running lazarus and programs compiled with
> lazarus. It's something that I never seen before and have no idea what
> to look at to resolve this problem.
> # /usr/bin/startlazarus
> -bash: /usr/bin/startlazarus: No such file or directory
> # ls -lL /usr/bin/startlazarus
> -rwxr-xr-x 1 root root 7807211 2005-12-04 16:50 /usr/bin/startlazarus
> # file /usr/bin/startlazarus
> /usr/bin/startlazarus: symbolic link to `../share/lazarus/startlazarus'
> # file /usr/share/lazarus/startlazarus
> /usr/share/lazarus/startlazarus: ELF 64-bit LSB executable, AMD
> x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked
> (uses shared libs), for GNU/Linux 2.4.0, not stripped
> # ldd /usr/share/lazarus/startlazarus
> /usr/bin/ldd: line 117: /usr/share/lazarus/startlazarus: No such file
> or directory
> Odd that it's reporting GNU/Linux 2.4.0 as I've just built fpc and
> lazarus and other programs report GNU/Linux 2.6.0:
> # file /bin/ls
> /bin/ls: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
> GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux
> 2.6.0, not stripped
> Anybody know what to look for?
More information about the cross-lfs