Re: qt5-qtwebengine-freeworld vs. aarch64
--- Begin Message ---
Vitaly Zaitsev via rpmfusion-developers wrote:
> On 24/01/2022 17:50, Kevin Kofler wrote:
>> Do you have any idea how we can resolve the issue or should I just go
>> back to building the package on x86_64 only?
>
> Take a look at the Telegram Desktop hacks:
> https://github.com/rpmfusion/telegram-desktop/blob/master/telegram-desktop.spec#L21-L25
Thank you for the pointer!
With these settings (under %ifarch aarch64):
# the RPM Fusion ARM builder runs out of memory during linking with the full
# setting below, and even with just force_debug_info, so omit all debuginfo
%global debug_config %{nil}
# reduce debug info even for the Qt parts to a minimum
%global optflags %(echo %{optflags} | sed 's/-g /-g1 /')
# tune down SMP to reduce memory use further
%global _smp_build_ncpus 6
I obtained a successful build of qt5-qtwebengine-freeworld on aarch64 in
5:38:48, less than half the 13:40:15 that chromium-freeworld took. So qt5-
qtwebengine-freeworld is no longer the slowest build in RPM Fusion. :-p
Kevin Kofler
___
rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
--- End Message ---
Re: qt5-qtwebengine-freeworld vs. aarch64
--- Begin Message --- Leigh Scott wrote: > You will need to disable debuginfo (use -g0) if your going to build > for aarch64. Oh fun, I looked at the offending command line, and it does attempt to pass -g0, but this is then overwritten by -g appended (twice, even) later, coming from the RPM optflags, it seems. This is the offending command line: /usr/bin/g++ -MMD -MF obj/QtWebEngineCore/content_browser_client_qt.o.d - DCHROMIUM_VERSION=\"87.0.4280.144\" -DUSE_UDEV -DUSE_AURA=1 - DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -DTOOLKIT_QT - D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE - DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG - DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DQT_NO_LINKED_LIST - DQT_NO_KEYWORDS -DQT_USE_QSTRINGBUILDER - DQ_FORWARD_DECLARE_OBJC_CLASS=QT_FORWARD_DECLARE_CLASS - DQTWEBENGINECORE_VERSION_STR=\"5.15.8\" - DQTWEBENGINEPROCESS_NAME=\"QtWebEngineProcess\" -DBUILDING_CHROMIUM - DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG - DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QMLMODELS_LIB -DQT_WEBCHANNEL_LIB - DQT_QML_LIB -DQT_NETWORK_LIB -DQT_POSITIONING_LIB -DQT_CORE_LIB - DQT_WEBENGINECOREHEADERS_LIB -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL - DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC - DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI - DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD - DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DWEBRTC_CHROMIUM_BUILD - DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 - DWEBRTC_USE_BUILTIN_ISAC_FIX=0 -DWEBRTC_USE_BUILTIN_ISAC_FLOAT=1 - DWEBRTC_USE_X11 -DWEBRTC_USE_X11 -DHAVE_SCTP -DNO_MAIN_THREAD_WRAPPING - DSK_CODEC_DECODES_PNG -DSK_CODEC_DECODES_WEBP -DSK_ENCODE_PNG - DSK_ENCODE_WEBP -DSK_USER_CONFIG_HEADER=\"../../skia/config/SkUserConfig.h\" -DSK_GL -DSK_CODEC_DECODES_JPEG -DSK_ENCODE_JPEG -DSK_USE_LIBGIFCODEC - DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VULKAN=1 - DSK_SUPPORT_GPU=1 - DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DCRASHPAD_ZLIB_SOURCE_EXTERNAL -DLEVELDB_PLATFORM_CHROMIUM=1 - DLEVELDB_PLATFORM_CHROMIUM=1 -DV8_COMPRESS_POINTERS - DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS -DV8_REVERSE_JSARGS - DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC - DUCHAR_TYPE=uint16_t -I../../3rdparty/chromium/skia/config - I../../3rdparty/chromium/third_party - I../../3rdparty/chromium/third_party/boringssl/src/include - I../../3rdparty/chromium/third_party/skia/include/core -Igen - I../../3rdparty/chromium -I/builddir/build/BUILD/qtwebengine-everywhere- src-5.15.8/src/core -I/builddir/build/BUILD/qtwebengine-everywhere- src-5.15.8/src/core/api -I/usr/include/qt5/QtQuick/5.15.2 - I/usr/include/qt5/QtQuick/5.15.2/QtQuick -I/usr/include/qt5/QtGui/5.15.2 - I/usr/include/qt5/QtGui/5.15.2/QtGui -I/usr/include/qt5 - I/usr/include/qt5/QtQuick -I/usr/include/qt5/QtGui - I/usr/include/qt5/QtQmlModels/5.15.2 - I/usr/include/qt5/QtQmlModels/5.15.2/QtQmlModels - I/usr/include/qt5/QtQml/5.15.2 -I/usr/include/qt5/QtQml/5.15.2/QtQml - I/usr/include/qt5/QtCore/5.15.2 -I/usr/include/qt5/QtCore/5.15.2/QtCore - I/usr/include/qt5/QtQmlModels -I/usr/include/qt5/QtWebChannel - I/usr/include/qt5/QtQml -I/usr/include/qt5/QtNetwork - I/usr/include/qt5/QtPositioning -I/usr/include/qt5/QtCore - I/builddir/build/BUILD/qtwebengine-everywhere-src-5.15.8/include - I/builddir/build/BUILD/qtwebengine-everywhere- src-5.15.8/include/QtWebEngineCore -I/builddir/build/BUILD/qtwebengine- everywhere-src-5.15.8/include/QtWebEngineCore/5.15.8 - I/builddir/build/BUILD/qtwebengine-everywhere- src-5.15.8/include/QtWebEngineCore/5.15.8/QtWebEngineCore -I.moc -Igen/.moc -I/usr/lib64/qt5/mkspecs/linux-g++ - I../../3rdparty/chromium/third_party/perfetto/include - Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen - Igen -Igen -I../../3rdparty/chromium/third_party/libyuv/include -Igen - I../../3rdparty/chromium/third_party/jsoncpp/source/include -Igen -Igen - Igen -Igen -Igen -Igen -Igen - I../../3rdparty/chromium/third_party/vulkan_headers/include -Igen -Igen - Igen -I../../3rdparty/chromium/third_party/khronos - I../../3rdparty/chromium/gpu -Igen/third_party/dawn/src/include - I../../3rdparty/chromium/third_party/dawn/src/include - I../../3rdparty/chromium/third_party/abseil-cpp - I../../3rdparty/chromium/third_party/boringssl/src/include - I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out - I../../3rdparty/chromium/third_party/ced/src - I../../3rdparty/chromium/third_party/protobuf/src - I../../3rdparty/chromium/third_party/webrtc_overrides - I../../3rdparty/chromium/third_party/webrtc -Igen/third_party/webrtc - I../../3rdparty/chromium/third_party/skia - I../../3rdparty/chromium/third_party/libgifcodec - I../../3rdparty/chromium/third_party/vulkan/include - I../../3rdparty/chromium/third_party/vulkan_headers/include - I../../3rdparty/chromium/third_party/crashpad/crashpad - I../../
Re: qt5-qtwebengine-freeworld vs. aarch64
--- Begin Message --- On 24/01/2022 17:50, Kevin Kofler wrote: Do you have any idea how we can resolve the issue or should I just go back to building the package on x86_64 only? Take a look at the Telegram Desktop hacks: https://github.com/rpmfusion/telegram-desktop/blob/master/telegram-desktop.spec#L21-L25 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org --- End Message ---
Re: qt5-qtwebengine-freeworld vs. aarch64
You will need to disable debuginfo (use -g0) if your going to build for aarch64. On 24/01/2022 16:50, Kevin Kofler via rpmfusion-developers wrote: ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
qt5-qtwebengine-freeworld vs. aarch64
--- Begin Message --- Hi, since chromium-freeworld, which is based on the same codebase and takes almost twice as long to build on x86_64 as qt5-qtwebengine-freeworld, has had several successful builds on aarch64: https://koji.rpmfusion.org/koji/packageinfo?packageID=506 I have decided to give qt5-qtwebengine-freeworld on aarch64 another try. Unfortunately, my 2 attempts so far have hit strange errors: 1. The first attempt built all the files coming from upstream Chromium, including several *jumbo*.cc ones that had caused trouble in the past, just fine, but then failed near the end building the Qt glue code: at 23703/23802, the build hit an OOM kill building obj/QtWebEngineCore/content_browser_client_qt.o: g++: fatal error: Killed signal terminated program cc1plus (This is one of the last files built as part of the Chromium build, then a successful build would move on to files built using qmake-qt5, which are not counted. But still, this is close to the end of the build process, and the heavy Chromium stuff has already been built at that point.) 2. The second attempt is even stranger: the aarch64 build task: https://koji.rpmfusion.org/koji/taskinfo?taskID=521517 got stuck in a really strange state where there is no log output anymore (there was at the beginning of the build, so it has vanished somewhere in the process). It looks like the builder crashed altogether. Do you have any idea how we can resolve the issue or should I just go back to building the package on x86_64 only? Kevin Kofler ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org --- End Message ---
