New to PLC Next Control. Executables, no such file or directory

PLCnext Technology & PLCnext Controls
1

In analyzing a AXC F 3152 I notice that my x-86 binaries will not run. This is despite them having the same attributes as the native binaries such as “ls” and “pwd”. Example:

root@axcf3152:/opt/nov/ngdaq# file /usr/bin/od.coreutils
/usr/bin/od.coreutils: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, BuildID[sha1]=2a54a1e57304de8cb25d1788f53552e0d7e0d59c, for GNU/Linux 3.2.0, stripped
root@axcf3152:/opt/nov/ngdaq# file ./Product
./Product: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=367150e9d3198210ae0f6d3b11f9a322a460a443, with debug_info, not stripped
root@axcf3152:/opt/nov/ngdaq# ./Product
-sh: ./Product: No such file or directory

2

I’m not sure if you closed this discussion, but if so I guess you found that the interpreter /lib64/ld-linux-x86-64.so.2 doesn’t exist - well, it exists, but in a different directory. So by creating the lib64 directory containing a symlink to the interpreter, the executable should be found.