From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12716] New: bio.h not found
Date: Sat, 28 Mar 2020 18:06:05 +0000 [thread overview]
Message-ID: <bug-12716-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12716
Bug ID: 12716
Summary: bio.h not found
Product: buildroot
Version: 2020.02
Hardware: PC
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: fshah48 at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8416
--> https://bugs.busybox.net/attachment.cgi?id=8416&action=edit
Output of make and stderr + output of find -name bio.h
I am rather new to linux.
Tried to build default configuration with minor changes required to produce ISO
image for running under qemu. I could update .config but it is 90KB and
restriction is 75KB.
<make menuconfig> failed because it could not find bio.h
I captured output of next attempt since it would produce only related output.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-28 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 18:06 bugzilla at busybox.net [this message]
2020-03-28 18:30 ` [Buildroot] [Bug 12716] bio.h not found 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-12716-163@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.