From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [NEXT] glibc: depends on host-bison
Date: Thu, 8 Feb 2018 23:50:07 +0100 [thread overview]
Message-ID: <20180208235007.45b8da07@windsurf.lan> (raw)
In-Reply-To: <20180207004849.21747-1-bluemrp9@gmail.com>
Hello,
On Tue, 6 Feb 2018 16:48:49 -0800, Ryan Coe wrote:
> 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>
I've improved the commit log a bit:
- To indicate which glibc upstream commit changed to making bison a
hard requirement. This allows to confirm it isn't an "accident" but
really an intentional move from glibc upstream.
- By replacing the error log by a reference to an autobuilder failure.
Thanks a lot for this fix, applied to next!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-08 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 0:48 [Buildroot] [NEXT] glibc: depends on host-bison Ryan Coe
2018-02-08 22:50 ` Thomas Petazzoni [this message]
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=20180208235007.45b8da07@windsurf.lan \
--to=thomas.petazzoni@bootlin.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