Building arm on aarch64

[Aleix Pol]

On Thu, Mar 30, 2017 at 10:53 AM, Tristan Van Berkom
<tristan.vanberkom at codethink.co.uk> wrote:
> On Wed, 2017-03-29 at 21:19 +0200, Aleix Pol wrote:
>> 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?
>> Thought so too.
>>
>> >
>> > Does running an arm binary work outside of flatpak?
>> I don't know, do you have one at hand? I'm not sure how it would work
>> myself.
>
> You should be able to test this with flatpak itself.
>
> Try using the regular steps to install the runtimes and some app from
> gnome-apps-nightly, using the "--arch=arm" arg to flatpak install/run
> etc to make sure you've installed the arm bundles.
>
> Or, if you recall the correct voodoo incantations for entering the
> runtime with a shell (I think can be done with flatpak build-init or
> such), then you can avoid downloading too much stuff, just try
> installing the arm runtime on your aarch64 machine, shell into it and
> run something.
>
> Sorry I still dont really have a clue what is going on, I also doubt
> this is the issue as Aarch64 is supposed to support 32bit execution
> mode (Aarch32) which in turn should support the armv7a tuning we use to
> build the runtime.
>
> Cheers,
>     -Tristan
>
>> >
>> > Also, is this the first module in the json, or did anything work
>> > before
>> > it failed?
>> Yes, first one.
>> _______________________________________________
>> xdg-app mailing list
>> xdg-app at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/xdg-app
>

Hi,
I reproduced it with the most basic test I could think of:

$ mkdir build
$ flatpak build-init build org.a.b.c org.freedesktop.Sdk
org.freedesktop.Platform 1.4 --arch arm
$ flatpak build build ls
execvp ls: Exec format error

Aleix