Hi!

Thanks for checking it out.

Yes, the transfer is ok, I verified it with md5sum.

So under “c library configuration” I am using “arm” as the “instruction set”. Now I changed it to “thumb” and I am now trying to make that boot again. But as a quick test, I uploaded one of these binaries from the new thumb-based root directory to my old OS and I get the exact same error… and I also uploaded that very same file to the official raspbian 9 OS and there it runs without problems.

Can you maybe tell if you are also using “thumb” or are using “arm” ?

May I ask, what commit and tasks are you using for your test you just did?

Best regards,
Tom,

On 28 Feb 2019, at 12:32, Diez B. Roggisch <deets@web.de> wrote:

The archive contains ARM architecture files, as Tom mentioned.

$ find . | xargs -L1 file
.: directory
./.DS_Store: Apple Desktop Services Store
./files: directory
./files/.DS_Store: Apple Desktop Services Store
./files/libcpu_extension.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=bca52678a3100264f856ae981378023a33ecf6c4, stripped
./files/libHeteroPlugin.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=0d135cf910571782588cae5a812358162dced8d2, stripped
./files/libinference_engine.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=7a8c112a128ff2bb84430c17323e774cc17ff8d9, stripped
./files/libmyriadPlugin.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=1106b14db6778bc4530768c40273a5f17af7cb7d, stripped
./files/mvnc: directory
./files/mvnc/MvNCAPI-ma2450.mvcmd: data
./files/mvnc/MvNCAPI-ma2480.mvcmd: data
./files/myriad_compile: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=4d7256a454df4b9a224ab5d9c3411d8741cd91d2, stripped

So there must be a different explanation. 

Can you verify that the file is properly transferred? Because for me on my PI3 I can run the program to a point where it gives me 

./myriad_compile: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

which is a later linker loading error.

Cheers,

Diez

On 28. Feb 2019, at 12:17, Martin Thomas <mtadk@hamtam.de> wrote:

Hi Tom,


you can not run x86 or amd64 programs on the arm processor natively. You have to compile it for arm or you will not be able to run it on the RPI.


Regards


Martin


Am 28.02.19 um 09:19 schrieb Tom Deblauwe:
Hello,

I am using a RPI3 B+ and using openadk successfully with the linux os using 4.14.71 kernel from raspberry pi itself. Now I am trying to run “openvino R5” which is an intel library that is only available as a precompiled so file for raspbian 9. It works indeed on raspbian 9.

But when I try to run their example demo file on my system, I get the error: 

# ./myriad_compile
mksh: ./myriad_compile: not executable: 32-bit ELF file

So now I want to debug that, but I’m out of ideas on how to proceed. 

just unpack it in the “package” directory to try it out.

So if you have any hints, I would really appreciate it.

I’m using glibc 2.27, with gcc 7.3.0 compiler.

Best regards,
Tom,


_______________________________________________
dev mailing list
dev@openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev