PLCnext AXC 2152 or 3152 and Microsoft Azure blob storage

Hey there!
We are trying to connect from a controller to Microsoft Azure blob storage, but we don’t get it working.

[list]
[*] First step was checking the tool "azcopy" with a windows machine and trying to copy files into Microsoft Azure blob storage. Which is working. Unfortunately we have no linux machine around for testing.

[*] Second step was trying the same from an AXC 2152 controller. Therefore I downloaded the linux tar-file in single steps like there:
[url="https://github.com/jeevan-vj/iamjeevan/blob/master/data/blog/upload-directroy-to-azure-storage-using-azcopy-linux.md"]https://github.com/jeevan-vj/iamjeevan/blob/master/data/blog/upload-directroy-to-azure-storage-using-azcopy-linux.md[/url]
After unzipping (tar) I put the file into an folder opt/plcnext/Azure and made it executeable (chmod +x). Then I tried with ssh connection to start the command (the one working on windows: azcopy list ...). Giving me a failure: command not found.
I guess the problem is that AXC 2152 is an 32 bit system and azcopy binaries are 64-bit.

[*] Third step was trying the same from an AXC3152 controller as they seem to be 64-bit ones. A good script for downloading an preparing is here:
[url="https://gist.github.com/aessing/76f1200c9f5b2b9671937b3b0ed5fd6f"]https://gist.github.com/aessing/76f1200c9f5b2b9671937b3b0ed5fd6f[/url]
But this also does not work. Giving the same error on ssh: command not found.
Useing the directory usr/bin/ the error changes to: no such file or directory
"whereis azcopy" gives /usr/bin/azcopy
"uname -m" gives x86_64
"file /usr/bin/azcopy" gives ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=XoZfP_hVSh_QjwTkjpCa/PfaLJW-BYygybLtxtoQ7/JDci8dRAhvuCPHVDDiWV/rXQXB1SH8ANxS727fsgT, not stripped
It seems that the interpreter is the problem here.
[/list]

Any ideas how to solve this efficiently? We are searching for a solution that works "out of box" as much as possible.
I think that's a good guess.  :)

[quote]It seems that the interpreter is the problem here.[/quote]
Yes, that's right.

The "simple" solution is to execute these two commands:


[code]mkdir /lib64
ln -sf /lib/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2[/code]
Right, that worked on the AXC 3152 even though I see no files named ld-linux...
So azcopy is working on an AXC 3152.

Could we get it working on an AXC 2152 too?
[code]>> uname -m
armv7l[/code]
I do not know what this armv7l is for a system. Azcopy is an open source tool, so possibilities should be there?

armv7l is an armv7 (32 bit) target.

I see that there are no suitable binaries provided on [url="https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10"]the Microsoft website[/url].

If the software is open source, then in theory it should be possible to cross-compile it for any PLCnext Control target, using the appropriate software development kit. In practice, I don't know how easy or difficult this would be - it depends partly on whether all the dependencies are included with the firmware (and hence in the SDK), or if one or more dependencies also need to be cross-compiled.