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: Sat, 04 Jan 2020 07:56:07 +0000 [thread overview]
Message-ID: <bug-12441-163-ZJAE0X3iGy@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12441-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12441
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #8 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Thanks for the report and the investigation. :-)
Note: sometimes, a package will need to build its own tools
during the build (e.g. to generate a table of values), and
those tools are built with the host compiler. Hence the
error. But qt5webengine already selects BR2_HOSTARCH_NEEDS_IA32_COMPILER
when needed, so this is strange...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-01-04 7:56 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
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 [this message]
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-ZJAE0X3iGy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox