Debian Jessie and "no target x86_64-linux"
lazarus / 1-Linux

----------------------------------------------------------------------
GPenguin · 2015-01-08 17:05

Hello,
I installed fpc and fpc-source via apt-get and built lazarus-ide from
source via SVN and the build process worked as expected. But when I
launched lazarus I got the following error:
"Compiler /usr/bin/fpc does not support target x86_64-linux"

More details can be taken from within this bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774839

I then fetched the SVN code of fpc and built that but for mysterious
reasons it always executes the old fpc from /usr/bin/fpc and not
~/bin/fpc and $PATH is set properly. I even tried to cut down $PATH to
/home/patrick/bin which results in this error then:
Error: ppcx64 can't be executed, error message: Failed to execute
"ppcx64", error code: 127

So I am stuck really bad.


Greetings,
GPenguin

----------------------------------------------------------------------
marcov · 2015-01-08 17:28

You could try to "strace" it, see what exactly goes wrong.

----------------------------------------------------------------------
GPenguin · 2015-01-08 19:51

Quote from: marcov on January 08, 2015, 06:28:35 pmYou could try to
"strace" it, see what exactly goes wrong.

"strace fpc" from a new user where $HOME was not changed:
http://paste.debian.net/139730/

and the "strace fpc" as user who built fpc from source with ~ as
target install:
http://paste.debian.net/139729/

Thanks for looking at this!


GPenguin

----------------------------------------------------------------------
Leledumbo · 2015-01-09 04:43

Quote from: GPenguin on January 08, 2015, 06:05:19 pmI then fetched
the SVN code of fpc and built that but for mysterious reasons it
always executes the old fpc from /usr/bin/fpc and not ~/bin/fpc and
$PATH is set properly. I even tried to cut down $PATH to
/home/patrick/bin which results in this error then:
Error: ppcx64 can't be executed, error message: Failed to execute
"ppcx64", error code: 127
fpc will try to execute ppcXXX residing in the same directory as it.
The ppcXXX itself is a symlink to actual ppcXXX residing somewhere
else. fpc doesn't actually output anything, so the first thing you
have to make sure is the symlink of ppcXXX correctly points to your
new ppcXXX.

----------------------------------------------------------------------
GPenguin · 2015-01-10 10:34

What I simply dont get is this:

[11:20:44 root@firefly:/usr/bin] ls -al ppc*
lrwxrwxrwx 1 root root 24 Jan  6 21:17 ppcx64 ->
/etc/alternatives/ppcx64
lrwxrwxrwx 1 root root 23 Oct 14 20:47 ppcx64-2.6.4 ->
../lib/fpc/2.6.4/ppcx64

[11:20:54 root@firefly:/usr/bin] ls -al fpc
lrwxrwxrwx 1 root root 21 Jan  6 21:17 fpc -> /etc/alternatives/fpc

[11:21:25 root@firefly:/usr/bin] ls -al /etc/fpc.cfg
lrwxrwxrwx 1 root root 25 Jan  6 21:17 /etc/fpc.cfg ->
/etc/alternatives/fpc.cfg

So I dont know where to point what. Because the local fpc.cfg I put in
~/bin without success.

----------------------------------------------------------------------
Leledumbo · 2015-01-10 16:35

Quote from: GPenguin on January 10, 2015, 11:34:35 amWhat I simply
dont get is this:

[11:20:44 root@firefly:/usr/bin] ls -al ppc*
lrwxrwxrwx 1 root root 24 Jan  6 21:17 ppcx64 ->
/etc/alternatives/ppcx64
lrwxrwxrwx 1 root root 23 Oct 14 20:47 ppcx64-2.6.4 ->
../lib/fpc/2.6.4/ppcx64

[11:20:54 root@firefly:/usr/bin] ls -al fpc
lrwxrwxrwx 1 root root 21 Jan  6 21:17 fpc -> /etc/alternatives/fpc

[11:21:25 root@firefly:/usr/bin] ls -al /etc/fpc.cfg
lrwxrwxrwx 1 root root 25 Jan  6 21:17 /etc/fpc.cfg ->
/etc/alternatives/fpc.cfg

So I dont know where to point what. Because the local fpc.cfg I put in
~/bin without success.
I have no idea how debian layouts the binaries and directories,
probably will need to understand /etc/alternatives purpose. I don't
use package manager version on whatever distro I have, only self build
from source, with bootstrapping compiler provided in sourceforge page.
And I don't customize the symlinks.