Hi there!
After installing some tools on my PLCnext AXC F 3152, I noticed that 64 bit binaries can’t be executed. I have tried this with the teleport node client (https://goteleport.com/docs/server-access/getting-started/) for example but I also noticed this with other binaries. This blogpost (https://www.plcnext-community.net/makersblog/installing-node-js-on-rfc-4072s/) also reports the same issue.
The workaround to fix this is to create a symlink /lib → /lib64:
sudo ln -sf /lib /lib64
The OS should however be able to execute 64 bit binaries out of the box because the OS seems to be operating in 64 bit. Is there a plan to fix this or is there a more elegant way to fix this?
Best regards, Florian
This is a common question that, as you have probably seen, has been discussed in other threads.
Here is some more detailed information:
PLCnext targets only support one architecture, e.g. 64 Bit for the AXC F 3152 or 32 Bit for the AXC F 2152. In cases of single-architecture platforms, it is standard to use the /lib folder, regardless of whether the platform is 32 bit or 64 bit. So, there is no „fix“ required, and this is unlikely to change.
The advice we have given in the past still applies:
1. If you build binaries using the correct SDK, then they will include the correct path to the interpreter.
2. We don't support the use of binaries that are not built using the SDK for the PLCnext Control device, but you're welcome to try.
3. There is a simple workaround for this issue (i.e. create a symbolic link called `/lib64` that points to `/lib`). An alternative work-around is to use the `patchelf` command on your binary, with the `--set-interpreter` option, to change the interpreter that is used by that binary.