From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [NEXT] glibc: depends on host-bison
Date: Tue, 6 Feb 2018 16:48:49 -0800 [thread overview]
Message-ID: <20180207004849.21747-1-bluemrp9@gmail.com> (raw)
Fixes the following build error:
checking for bison... no
checking if ./buildroot/output/host/bin/arm-rpi1-linux-gnueabihf-gcc is sufficient to build libc... yes
checking for arm-rpi1-linux-gnueabihf-nm... ./buildroot/output/host/bin/arm-rpi1-linux-gnueabihf-nm
checking for python3... python3
configure: error:
*** These critical programs are missing or too old: bison
*** Check the INSTALL file for required versions.
package/pkg-generic.mk:237: recipe for target './buildroot/output/build/glibc-glibc-2.27/.stamp_configured' failed
make: *** [./buildroot/output/build/glibc-glibc-2.27/.stamp_configured] Error 1
Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
---
package/glibc/glibc.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
index b674191b22..00e114566c 100644
--- a/package/glibc/glibc.mk
+++ b/package/glibc/glibc.mk
@@ -28,7 +28,7 @@ GLIBC_ADD_TOOLCHAIN_DEPENDENCY = NO
# Before glibc is configured, we must have the first stage
# cross-compiler and the kernel headers
-GLIBC_DEPENDENCIES = host-gcc-initial linux-headers host-gawk
+GLIBC_DEPENDENCIES = host-gcc-initial linux-headers host-bison host-gawk
GLIBC_SUBDIR = build
--
2.15.1
next reply other threads:[~2018-02-07 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 0:48 Ryan Coe [this message]
2018-02-08 22:50 ` [Buildroot] [NEXT] glibc: depends on host-bison Thomas Petazzoni
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=20180207004849.21747-1-bluemrp9@gmail.com \
--to=bluemrp9@gmail.com \
--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