Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 02 Jan 2020 19:28:53 +0000	[thread overview]
Message-ID: <bug-12441-163-UH4MpGkFgz@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 #6 from Bartosz Bilas <bartosz.bilas@hotmail.com> ---
(In reply to Aleksandr Makarov from comment #5)

Hello Aleksandr,
I've built your config successfully on my machine without any problems so I
don't think there is something wrong with buildroot itself. I was googling a
bit and it looks like a missing development stuff on your machine. Which OS do
you use to build that image? Please also check if you have installed userspace
headers from the Linux kernel.

Best
Bartek

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-01-02 19:28 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 [this message]
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-UH4MpGkFgz@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