Re: [Buildroot] [PATCH v3 1/3] package/qt5/qt5webengine-chromium-catapult: new package

[James Hilliard <james.hilliard1@gmail.com>]

On Wed, Jan 12, 2022 at 5:56 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello James,
>
> On Thu,  6 Jan 2022 21:55:29 -0700
> James Hilliard <james.hilliard1@gmail.com> wrote:
>
> > This version of catapult is python3 compatible and will be used to
> > replace the python2 only version in qt5webengine-chromium.
> >
> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > ---
> > Changes v2 -> v3:
> >   - add kconfig entry
> > ---
> >  package/qt5/Config.in                              |  1 +
> >  .../qt5/qt5webengine-chromium-catapult/Config.in   |  4 ++++
> >  .../qt5webengine-chromium-catapult.hash            |  3 +++
> >  .../qt5webengine-chromium-catapult.mk              | 14 ++++++++++++++
> >  4 files changed, 22 insertions(+)
> >  create mode 100644 package/qt5/qt5webengine-chromium-catapult/Config.in
> >  create mode 100644 package/qt5/qt5webengine-chromium-catapult/qt5webengine-chromium-catapult.hash
> >  create mode 100644 package/qt5/qt5webengine-chromium-catapult/qt5webengine-chromium-catapult.mk
>
> I have tested this patch series (I'm replying to the v3 because that's
> the one I tested) with the following defconfig:
>
> BR2_arm=y
> BR2_arm1176jzf_s=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
> BR2_PACKAGE_QT5=y
> BR2_PACKAGE_QT5WEBENGINE=y
> BR2_PACKAGE_RPI_USERLAND=y
>
> and it failed to build like this:

Yeah, there's quite a few issues with the qt5webengine update build in
general, I've
split out the kde qt5 deps update so that it can be
reviewed/tested/merged before the
qt5webengine update as the other updates require much more minimal changes and
should make it easier to test the qt5webengine update issues
separately once the kde
are verified to not create regressions:
https://patchwork.ozlabs.org/project/buildroot/patch/20220113000935.2353800-1-james.hilliard1@gmail.com/

I also think I fixed a potentially related issue with qmake sysrootify
path generation by
disabling it and setting sysroot paths manually, this seems to work
better and appears
to fix per-package directory builds on a number of the qt5
modules(although some seem
to still have issues), this should hopefully make it easier to fix the
qt5webengine issues
as well:
https://patchwork.ozlabs.org/project/buildroot/patch/20220112203939.606775-1-james.hilliard1@gmail.com/

Both of these should apply on top of master and should not depend on each other.

>
> FAILED: host/obj/crypto/crypto/nss_key_util.o
> /usr/bin/g++ -MMD -MF host/obj/crypto/crypto/nss_key_util.o.d -DCRYPTO_IMPLEMENTATION -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 -Ihost/gen -I../../3rdparty/chromium -I../../3rdparty/chromium/third_party/perfetto/include -Ihost/gen/third_party/perfetto/build_config -Ihost/gen/third_party/perfetto -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/third_party/abseil-cpp -I../../3rdparty/chromium/third_party/protobuf/src -Ihost/gen/protoc_out -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-poin
 te
>  r-checks -Wno-comments -Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -I/usr/include/nss -I/usr/include/nspr -std=gnu++14 -Wno-narrowing -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type -Wno-deprecated-copy -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -I/home/thomas/buildroot/buildroot/output/host/include -c ../../3rdparty/chromium/crypto/nss_key_util.cc -o host/obj/crypto/crypto/nss_key_util.o
> In file included from ../../3rdparty/chromium/crypto/nss_key_util.cc:5:
> ../../3rdparty/chromium/crypto/nss_key_util.h:8:10: fatal error: secoidt.h: No such file or directory
>     8 | #include <secoidt.h>
>       |          ^~~~~~~~~~~
> compilation terminated.
> [19912/23484] CXX host/obj/crypto/crypto/sha2.o
> [19913/23484] CXX host/obj/crypto/crypto/secure_hash.o
> [19914/23484] CXX host/obj/base/base/base_jumbo_7.o
> [19915/23484] CXX host/obj/crypto/crypto/signature_creator.o
> [19916/23484] CXX host/obj/base/base/base_jumbo_11.o
> [19917/23484] CXX host/obj/crypto/crypto/symmetric_key.o
> [19918/23484] CXX host/obj/crypto/crypto/signature_verifier.o
> [19919/23484] CXX host/obj/base/base/base_jumbo_4.o
> In file included from host/gen/base/base_jumbo_4.cc:6:
> ./../../3rdparty/chromium/base/debug/alias.cc:11: warning: ignoring #pragma clang max_tokens_here [-Wunknown-pragmas]
>    11 | #pragma clang max_tokens_here 250
>       |
> ninja: build stopped: subcommand failed.
> make[5]: *** [Makefile.gn_run:356: run_ninja] Error 1
> make[4]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
> make[3]: *** [Makefile:79: sub-core-make_first] Error 2
> make[2]: *** [Makefile:49: sub-src-make_first] Error 2
> make[1]: *** [package/pkg-generic.mk:295: /home/thomas/buildroot/buildroot/output/build/qt5webengine-5.15.8/.stamp_built] Error 2
> make: *** [Makefile:84: _all] Error 2
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot