From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3 v3] linux: kconfig needs host-{flex, bison} to build the configurators
Date: Tue, 14 Aug 2018 23:12:30 +0200 [thread overview]
Message-ID: <20180814231230.7f5e2e3e@windsurf> (raw)
In-Reply-To: <20180814210349.GN7915@scaer>
Hello,
On Tue, 14 Aug 2018 23:03:49 +0200, Yann E. MORIN wrote:
> > So the system-wide bison/flex would only be used for the kconfig
> > programs built by Buildroot itself (if we move to a newer kconfig
> > version that doesn't have the pre-generated files) or by
> > Linux/U-Boot/Busybox/Barebox. Any other use of flex/bison would use
> > host-flex and host-bison. That's your proposal ?
>
> Yes, that is my proposal.
OK. Let's see what Arnout/Peter have to say about this. If they don't
express any opinion by Thursday, I'll go with your proposal which seems
reasonable to me.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-14 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 20:16 [Buildroot] [PATCH 0/3 v3] core/pkg-kconfig: ensure we have necessary tools to run configurators Yann E. MORIN
2018-08-03 20:16 ` [Buildroot] [PATCH 1/3 v3] core/pkg-kconfig: allow dependencies before configurators Yann E. MORIN
2018-08-07 10:22 ` Jan Kundrát
2018-08-03 20:16 ` [Buildroot] [PATCH 2/3 v3] linux: kconfig needs host-{flex, bison} to build the configurators Yann E. MORIN
2018-08-07 10:21 ` Jan Kundrát
2018-08-14 14:21 ` Thomas Petazzoni
2018-08-14 15:27 ` Yann E. MORIN
2018-08-14 19:53 ` Thomas Petazzoni
2018-08-14 21:03 ` Yann E. MORIN
2018-08-14 21:12 ` Thomas Petazzoni [this message]
2018-08-14 22:50 ` Arnout Vandecappelle
2018-08-15 12:18 ` Thomas Petazzoni
2018-08-15 16:00 ` Yann E. MORIN
2018-08-16 15:50 ` Arnout Vandecappelle
2018-08-03 20:16 ` [Buildroot] [PATCH 3/3 v3] linux: kconfig needs the toolchain Yann E. MORIN
2018-08-07 10:21 ` Jan Kundrát
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=20180814231230.7f5e2e3e@windsurf \
--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