All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:21:30 +0200	[thread overview]
Message-ID: <20180814162130.00f55418@windsurf> (raw)
In-Reply-To: <c85b3d3994261356bedfa3daeaddbc4329836fe9.1533327111.git.yann.morin.1998@free.fr>

Hello,

On Fri,  3 Aug 2018 22:16:55 +0200, Yann E. MORIN wrote:
> Take this opportunity to also drop the append-assignment as the first
> assignment to LINUX_DEPENDENCIES.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

I am a bit confused. In this series, you suggest to make
host-flex/host-bison dependencies of the configuration step of Linux.
But in another series
(http://patchwork.ozlabs.org/project/buildroot/list/?series=59260), you
suggest to make flex/bison hard requirements of Buildroot, so that we
don't have to build them.

Could you clarify in which direction you would like to go ? Also, if we
make bison/flex hard requirements of Buildroot, I'd like to have a
clear rule on whether we keep or not our host-bison/host-flex packages,
and if we keep them, when they should be used vs. when the system
bison/flex should be used.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-08-14 14:21 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 [this message]
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
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=20180814162130.00f55418@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 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.