Building arm on aarch64

[Aleix Pol]

On Wed, Mar 29, 2017 at 9:14 PM, Alexander Larsson <alexl at redhat.com> wrote:
> On Wed, 2017-03-29 at 20:12 +0200, Aleix Pol wrote:
>> Hi,
>> As you can see, my endeavour isn't over just yet.
>>
>> Gnome kindly gave me access to an aarch64 system (much appreciated!)
>> where I've been trying to get the build sorted.
>>
>> I'm using flatpak-build-tools to get things working on that system.
>> aarch64 seems to work just fine, arm builds don't seem to prosper
>> that
>> well.
>>
>> This is the build.conf I'm using nowadays:
>> https://paste.kde.org/piy2zsqpp/9kkvy0/raw
>>
>> flatpak-builder is being called like this:
>> flatpak-builder --arch=arm --force-clean --require-changes --ccache
>> --repo=/srv/gnome_aarch64/flatpak-build-scripts/work/export/repo
>> --subject="build of org.kde.Sdk, `date`"  sdk org.kde.Sdk.json
>>
>> That's the error I'm getting:
>> HEAD is now at a55f362... Fix the JPEG EXIF reader to deal with some
>> broken/corrupt files
>> execvp ./configure: Exec format error
>> Error: module qt5-qtbase: Child process exited with code 1
>> make: *** [all] Error 1
>
> This looks like its trying to run an unsupported elf format bash (or
> whatever shell the configure file references). That is weird though, I
> thought aarch64 machines always could run arm executables?
>
> Does running an arm binary work outside of flatpak?

I also tried executing a bare arm helloworld, it didn't work:
$ ./hello
-bash: ./hello: cannot execute binary file

I have discussing the issue with a colleague who is has been working
with arm for a while and he told me there's some aarch64 systems that
don't support armhf execution.

I'll keep digging...

Aleix