Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
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 17:27:43 +0200	[thread overview]
Message-ID: <20180814152743.GJ7915@scaer> (raw)
In-Reply-To: <20180814162130.00f55418@windsurf>

Thomas, All,

On 2018-08-14 16:21 +0200, Thomas Petazzoni spake thusly:
> 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 ?

This very series is about solving a technical problem, that
kconfig-based packages may have dependencies required even before
running the configurators.

On the other hand, that other series is about changing our requirements.

If we decide to require flex+bison, so in this series, only patch 2 can
be dropped.

> 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.

My position is that we will always want to have our host flex and bison
to build packages that install things in host/, in staging/ or in
target/.

For the linux kernel and other kconfig-based packages, we don't care
which flex/bison are used, because the resulting binaries are not
installed, unless those packages also generate code eventually installed
in host/, staging/ or target/

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-08-14 15:27 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 [this message]
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=20180814152743.GJ7915@scaer \
    --to=yann.morin.1998@free.fr \
    --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