From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12441] qt5webengine build error: asm/errno.h: No such file or directory
Date: Wed, 01 Jan 2020 13:44:16 +0000 [thread overview]
Message-ID: <bug-12441-163-EOyICjHI6a@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12441-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12441
--- Comment #2 from Aleksandr Makarov <seems.deviant@gmail.com> ---
(In reply to Bartosz Bilas from comment #1)
Bartek,
The mentioned error occurs every time I do either full build with 'make all' or
rebuilding with 'make qt5webengine-dirclean qt5webengine-rebuild'.
I use the Github [1] mirror as buildroot source. My HEAD is on '35c040d1ab
boot/uboot: cover more u-boot versions when fixing up libfdt include paths';
that's where I can reproduce the issue right now.
I can also see that the patch [2] you mentioned is applied to the
src/3rdparty/chromium/build/config/linux/pkg_config.gni in my build directory.
However it does not seem to address this exact issue as none of the failing
object files compile with '-isystem' flag.
[1] https://github.com/buildroot/buildroot
[2]
https://github.com/buildroot/buildroot/commit/6cfe21ae90ccd88254bf5240b2b29d74794f45fe
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-01-01 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 15:08 [Buildroot] [Bug 12441] New: qt5webengine build error: asm/errno.h: No such file or directory bugzilla at busybox.net
2019-12-30 18:42 ` [Buildroot] [Bug 12441] " bugzilla at busybox.net
2020-01-01 13:44 ` bugzilla at busybox.net [this message]
2020-01-01 19:16 ` bugzilla at busybox.net
2020-01-01 22:31 ` bugzilla at busybox.net
2020-01-01 22:33 ` bugzilla at busybox.net
2020-01-02 19:28 ` bugzilla at busybox.net
2020-01-03 19:58 ` bugzilla at busybox.net
2020-01-04 7:56 ` bugzilla at busybox.net
2020-01-05 19:23 ` Arnout Vandecappelle
2020-01-04 10:42 ` bugzilla at busybox.net
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=bug-12441-163-EOyICjHI6a@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.