[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-03-29 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #12 from Jan Grulich  ---
(In reply to mirh from comment #11)
> (In reply to Jan Grulich from comment #9)
> > The reason why we disabled them was to avoid hardcoding kernel version
> > requirements. With all those enabled, Qt build was requiring kernel 3.17.y
> > or something like that, why without those enabled it was kernel 2.x.
> 
> If I look at the sources, that was never committed though. 
> 
> I can only see bug 403042 which pertains flatpak specifically, but qt-base
> is still untouched to this day. I just banged my head like two afternoons
> before realizing sddm wasn't booting on 3.16 due to this.

This was pushed only to our Flatpak builds, not to upstream.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-03-29 Thread mirh
https://bugs.kde.org/show_bug.cgi?id=416262

mirh  changed:

   What|Removed |Added

 CC||m...@protonmail.ch

--- Comment #11 from mirh  ---
(In reply to Jan Grulich from comment #9)
> The reason why we disabled them was to avoid hardcoding kernel version
> requirements. With all those enabled, Qt build was requiring kernel 3.17.y
> or something like that, why without those enabled it was kernel 2.x.

If I look at the sources, that was never committed though. 

I can only see bug 403042 which pertains flatpak specifically, but qt-base is
still untouched to this day. I just banged my head like two afternoons before
realizing sddm wasn't booting on 3.16 due to this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-31 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #10 from Rinigus  ---
Re disabling statx:

I am arguing that the patch which you use to disable statx is not working. As
such, you have statx enabled right now.

If you try to build KDE runtime for arm using QEMU, it will fail quite early as
soon as qmake is created. And it will fail due to the missing statx in
QEMU/arm, as it looks to me.

So, by enabling statx, you are making it impossible to compile for ARM using
qmake and on regular workstations. 

For me 5.13 doesn't work either and this time nor with qmake nor cmake -
basically no way to build. Can't tell whether cmake failure is also statx
related, as they seem to have some checks for permissions:
https://github.com/Kitware/CMake/blame/master/Utilities/cmlibuv/src/unix/fs.c#L1154

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-31 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=416262

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #9 from Jan Grulich  ---
Maybe statx doesn't need to be disabled anymore with Qt 5.13. I will try to
build it with and without disabled statx and verify it.

The reason why we disabled them was to avoid hardcoding kernel version
requirements. With all those enabled, Qt build was requiring kernel 3.17.y or
something like that, why without those enabled it was kernel 2.x.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-30 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

Rinigus  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #8 from Rinigus  ---
I am reopening it as I think that statx call was expected to be disabled.

Namely, I believe we are hitting issue in QEMU
https://bugs.launchpad.net/qemu/+bug/1861341 . As a result, we cannot use qmake
(I suspect that https://invent.kde.org/kde/flatpak-kde-runtime/issues/3 was
caused by the same issue).

Looks like you tried to disable statx and rename2 in 
https://invent.kde.org/kde/flatpak-kde-runtime/blob/qt5.12lts/patch/qtbase-avoid-hardcoding-kernel-version.patch

However, statx is disabled only for Android in Qt:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp?h=5.12#n98
. For Linux, it looks like it will depend on local sources. So, if we wish to
disable statx, we would have to ensure that
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp?h=5.12#n313
will fail. 

I guess a patch with "#undef STATX_BASIC_STATS" in somewhere after includes in
qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp would resolve it.

If you think that its inappropriate to reopen it and should be closed, please
do so. As such, its not KDE Flatpak bug, but workaround for qemu issue. But it
does hinder development with the runtime.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-20 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #7 from Rinigus  ---
I think I have been hitting some issue with statx system call which is
triggered in QEMU or ARM32. Haven't looked deeper, but look to be related:

https://bugreports.qt.io/browse/QTBUG-64490
https://bugreports.qt.io/browse/QTBUG-68205
https://bugreports.qt.io/browse/QTBUG-66930

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-19 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=416262

Aleix Pol  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #6 from Aleix Pol  ---
Alright, closing for now. Thanks for reaching out anyway, glad you're using the
runtime! :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-18 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #5 from Rinigus  ---
Feel free to close as it looks to be an issue with my emulation environment.
When running on native platform, all works as expected. I will have to figure
out meanwhile what's wrong in my setup, but that's not related to KDE Flatpak
environment as such.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-17 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #4 from Rinigus  ---
It maybe some issue with my local setup. On Flathub servers, all is working as
expected. I keep the issue open for now, will try to figure out what's going
on.

If someone can test cross-building of ARM package (as attached), would be great
to know the results.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-16 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #3 from Rinigus  ---
I will look into it and will report back

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-15 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #2 from Aleix Pol  ---
Would you be able to investigate a bit what could be wrong? I'm quite clueless
myself about qmake. :/

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-14 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #1 from Rinigus  ---
Same issue is observed for KDE 5.13

-- 
You are receiving this mail because:
You are watching all bug changes.

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-01-14 Thread Rinigus
https://bugs.kde.org/show_bug.cgi?id=416262

Rinigus  changed:

   What|Removed |Added

 CC||rinigus@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.