https://bugs.kde.org/show_bug.cgi?id=416262
Rinigus <rinigus....@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
--- Comment #8 from Rinigus <rinigus....@gmail.com> ---
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.
