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] [RFC] [PATCH v2 2/2] support/kconfig: Bump to kconfig from Linux 4.17-rc2
Date: Sun, 20 May 2018 16:23:11 +0200	[thread overview]
Message-ID: <20180520142311.GA3453@scaer> (raw)
In-Reply-To: <20180519230311.6a3652fd@windsurf>

Thomas, All,

On 2018-05-19 23:03 +0200, Thomas Petazzoni spake thusly:
> If we were to drop the *shipped files, it means we would have to build
> host-flex and host-bison prior to running any "make *config" command.
> This would be really annoying.

And would requier quite a rework of the main Makefile, since we do not
include that pcakge .mk files until we do have a .coinfig file. So
currently, we can't have host-{flex,bison} before we have a .config.

Regards,
Yann E. MORIN.

> Alternatively, we could decide to make
> "flex" and "bison" mandatory dependencies of Buildroot, and rely on the
> user to install them on the system rather than building them ourselves.
> The drawback of this is that we would no longer control which version
> of flex/bison gets used.
> 
> Best regards,
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com

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

  parent reply	other threads:[~2018-05-20 14:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 16:44 [Buildroot] [PATCH v2 1/2] support/kconfig: Add missing target to README.buildroot Petr Vorel
2018-05-09 16:44 ` [Buildroot] [RFC] [PATCH v2 2/2] support/kconfig: Bump to kconfig from Linux 4.17-rc2 Petr Vorel
2018-05-19 21:03   ` Thomas Petazzoni
2018-05-20  5:05     ` Petr Vorel
2018-05-20 14:23     ` Yann E. MORIN [this message]
2018-05-20 14:31       ` Petr Vorel
2018-05-20 14:41         ` Yann E. MORIN
2018-05-20 14:50           ` Thomas Petazzoni
2018-05-22 21:22             ` Arnout Vandecappelle
2018-05-28 20:37               ` Yann E. MORIN
2018-05-29 10:44                 ` Arnout Vandecappelle
2018-05-29 17:04                   ` Yann E. MORIN
2018-07-30 13:04                   ` Thomas Petazzoni
2018-07-31  7:55                     ` Arnout Vandecappelle
2018-07-31  8:06                       ` Thomas Petazzoni
2018-07-31  8:20                         ` Arnout Vandecappelle
2018-08-01 19:42                           ` Yann E. MORIN
2018-08-01 20:20                             ` Yann E. MORIN
2018-08-02 11:02                             ` Arnout Vandecappelle
2018-08-02 17:10                               ` Yann E. MORIN
2018-08-03 16:24                                 ` Yann E. MORIN
2018-05-09 16:46 ` [Buildroot] [PATCH v2 1/2] support/kconfig: Add missing target to README.buildroot Petr Vorel
2018-05-13 20:09 ` 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=20180520142311.GA3453@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