Digging ARM, old gcc
Aleix Pol
aleixpol at kde.org
Fri Aug 11 18:37:40 UTC 2017
On Tue, Jul 25, 2017 at 9:31 AM, Alexander Larsson <alexl at redhat.com> wrote:
> On Tue, 2017-07-11 at 18:47 +0200, Aleix Pol wrote:
>> Hi,
>> I've been pulling the thread on the QtWebEngine again now that 5.9
>> was
>> released and found a different issue:
>> https://bugreports.qt.io/browse/QTBUG-61846
>>
>> In this bug report Kofler suggests that our gcc (6.2.0) may be having
>> an issue, do you know if we could maybe be shipping a newer one? I
>> don't see an advantage in having an old compiler.
>> I'm not sure which version fixes the issue, if you think it's worth
>> it
>> I can figure it out.
>
> We inherit gcc from the yocto base, and while there is nothing that
> prohibits us from fixin particular bugs in that I don't want to just
> change to a massively different version, because that could expose
> issues (build and runtime) in other parts of the runtime. I want to use
> the same version that upstream yocto tested against.
>
> However, I know there is one arm specific thing in our compilers that
> is a bit different from what is common. It does not enable "thumb" mode
> by default. That causes some issues with GtkWebkit i believe. You can
> try adding -mthumb to CPPFLAGS and see if this affects anything.
I managed to build it in the end, here's the patch for the curious:
https://commits.kde.org/flatpak-kde-runtime/d016215d753b6178fe615f92263eb4d693ef204a
I'll be mostly AFK for the next 2 weeks, I'll look into setting up
regular builders for the other architectures when I'm back.
Cheers!
Aleix
More information about the Flatpak
mailing list