From: Peter Seiderer <ps.report@gmx.net>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Julien Corjon <corjon.j@ecagroup.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/qt5/qt5base: disable broken qmake sysrootify
Date: Sun, 16 Jan 2022 10:19:01 +0100 [thread overview]
Message-ID: <20220116101901.23db5faa@gmx.net> (raw)
In-Reply-To: <CADvTj4pFsYA+vaz4k6Fru9KnuRUeHmZ6QhQP_WJsxS+kHy1qdw@mail.gmail.com>
Hello James,
On Sat, 15 Jan 2022 22:08:57 -0700, James Hilliard <james.hilliard1@gmail.com> wrote:
> On Sat, Jan 15, 2022 at 3:37 PM Peter Seiderer <ps.report@gmx.net> wrote:
> >
> > Hello James, *,
> >
> > On Wed, 12 Jan 2022 13:39:39 -0700, James Hilliard <james.hilliard1@gmail.com> wrote:
> >
> > > Currently the qmake gcc sysrootify path logic causes issues with
> > > per-package directories, disable automatic gcc sysroot for qt5base
> > > install and override all qt.conf paths manually to point to their
> > > correct locations.
> > >
> > > Redirect HostData to STAGING_DIR as mkspecs need to be available there
> > > instead of the HOST_DIR for cross compilation to work.
> > >
> > > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > > ---
> > > package/qt5/qt5base/qt.conf.in | 18 +++++++++++++++---
> > > package/qt5/qt5base/qt5base.mk | 2 ++
> > > 2 files changed, 17 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/package/qt5/qt5base/qt.conf.in b/package/qt5/qt5base/qt.conf.in
> > > index 2215cbd4e1..db9ab0c364 100644
> > > --- a/package/qt5/qt5base/qt.conf.in
> > > +++ b/package/qt5/qt5base/qt.conf.in
> > > @@ -2,6 +2,18 @@
> > > Prefix=/usr
> > > HostPrefix=@@HOST_DIR@@
> > > Sysroot=@@STAGING_DIR@@
> > > -Headers=/usr/include/qt5
> > > -Plugins=/usr/lib/qt/plugins
> > > -Examples=/usr/lib/qt/examples
> > > +SysrootifyPrefix=false
> > > +Binaries=@@STAGING_DIR@@/usr/bin
> > > +Libraries=@@STAGING_DIR@@/usr/lib
> > > +Headers=@@STAGING_DIR@@/usr/include/qt5
> > > +Plugins=@@STAGING_DIR@@/usr/lib/qt/plugins
> > > +Examples=@@STAGING_DIR@@/usr/lib/qt/examples
> > > +Data=@@STAGING_DIR@@
> > > +Translations=@@STAGING_DIR@@/translations
> > > +ArchData=@@STAGING_DIR@@/usr
> > > +LibraryExecutables=@@STAGING_DIR@@/usr/libexec
> > > +Imports=@@STAGING_DIR@@/usr/imports
> > > +Qml2Imports=@@STAGING_DIR@@/usr/qml
> > > +HostBinaries=@@HOST_DIR@@/bin
> > > +HostLibraries=@@HOST_DIR@@/lib
> > > +HostData=@@STAGING_DIR@@
> > > diff --git a/package/qt5/qt5base/qt5base.mk b/package/qt5/qt5base/qt5base.mk
> > > index bcdf036f00..6c05e710d8 100644
> > > --- a/package/qt5/qt5base/qt5base.mk
> > > +++ b/package/qt5/qt5base/qt5base.mk
> > > @@ -311,8 +311,10 @@ define QT5BASE_CONFIGURE_CMDS
> > > -v \
> > > -prefix /usr \
> > > -hostprefix $(HOST_DIR) \
> > > + -hostdatadir $(STAGING_DIR) \
> > > -headerdir /usr/include/qt5 \
> > > -sysroot $(STAGING_DIR) \
> > > + -no-gcc-sysroot \
> > > -plugindir /usr/lib/qt/plugins \
> > > -examplesdir /usr/lib/qt/examples \
> > > -no-rpath \
> >
> > This one leads to the following compile failure for qt5webengine-5.15.2:
> >
> > .../host/lib/gcc/arm-buildroot-linux-gnueabihf/10.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld: cannot find crti.o: No such file or directory
> > collect2: error: ld returned 1 exit status
>
> So I was able to reproduce this error, however best I can tell it's
> probably not a regression
This is a known failure, see the patches adding host-freetype/host-libjepeg/host-harfbuzz ([1])
or your own qt5webengine bump adding host-freetype dependency ([2])...
Additional the SIGSTKSZ fix is needed...
Regards,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2022-January/634005.html
[2] http://lists.busybox.net/pipermail/buildroot/2022-January/633439.html
> as the compilation still fails due to a different error without this patch:
>
> ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned
> non-zero exit code.
> pkgresult = exec_script(pkg_config_script, args, "value")
> ^----------
> Current dir: /home/buildroot/buildroot/output/build/qt5webengine-5.15.2/src/core/release/
> Command: /home/buildroot/buildroot/output/host/bin/python2
> /home/buildroot/buildroot/output/build/qt5webengine-5.15.2/src/3rdparty/chromium/build/config/linux/pkg-config.py
> -p /home/buildroot/buildroot/output/build/qt5webengine-5.15.2/host-bin/host-pkg-config
> libjpeg
> Returned 1.
> stderr:
>
> Package libjpeg was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libjpeg.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libjpeg', required by 'virtual:world', not found
> Could not run pkg-config.
>
> See //third_party/BUILD.gn:17:3: whence it was called.
> pkg_config("system_libjpeg") {
> ^-----------------------------
> See //third_party/blink/renderer/platform/BUILD.gn:159:5: which caused
> the file to be included.
> "//third_party:jpeg",
> ^-------------------
> Project ERROR: GN run error!
>
> >
> >
> > But the file crti.o exists:
> >
> > $ find . -name crti.o
> > ./build/glibc-2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4/build/csu/crti.o
> > ./host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/crti.o
> >
> >
> > Did not (yet) test with your latest (v2) patch iteration...
> >
> > Compile with qt5webengine bump to 5.15.8-lts fails already before the linking stage
> > (see secoidt.h/pk11pub.h No such file or directory failure reported by already by
> > Thomas)...
> >
> > Regards,
> > Peter
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-16 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 20:39 [Buildroot] [PATCH 1/1] package/qt5/qt5base: disable broken qmake sysrootify James Hilliard
2022-01-13 19:44 ` Thomas Petazzoni
2022-01-14 4:51 ` James Hilliard
2022-01-15 22:37 ` Peter Seiderer
2022-01-16 1:34 ` James Hilliard
2022-01-16 5:08 ` James Hilliard
2022-01-16 9:19 ` Peter Seiderer [this message]
2022-01-16 10:28 ` James Hilliard
2022-01-16 10:45 ` James Hilliard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220116101901.23db5faa@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=james.hilliard1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox