All of 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: Mon, 28 May 2018 22:37:43 +0200	[thread overview]
Message-ID: <20180528203743.GK2965@scaer> (raw)
In-Reply-To: <dcf8150e-1eb1-ba10-09e6-d3eb0bffaf2b@mind.be>

Arnout, Thomas, All,

On 2018-05-22 23:22 +0200, Arnout Vandecappelle spake thusly:
> On 20-05-18 16:50, Thomas Petazzoni wrote:
> > Hello,
> > 
> > On Sun, 20 May 2018 16:41:41 +0200, Yann E. MORIN wrote:
> > 
> >> I initially did not reply further to this part, becuase I seem to
> >> remember that there was a change in behavious with certain versions of
> >> flex/bison, that made the output change drastically, and I was afraid we
> >> could be bitten by this...
> >>
> >> But in the end, this is not a problem, because we would not care to
> >> mix-n-match files built with different versions of said tools, as they
> >> would be those from the distro, always, and never those we ship, since
> >> we would no longer ship them.
> >>
> >> And eventually, I now remember that the issue was with gperf changing
> >> its API (a function prototype changed), and that was causing pain. But
> >> now, kconfig no longer uses gperf to start with, so no incompatibility
> >> anymore anyway.
> >>
> >> Which would allow us to drop the dependency of linux on host-{flex,bison}
> >> that we had to add recently.
> > 
> > If we start relying on the system-installed flex and bison, then we
> > should remove host-flex and host-bison entirely, not only for the linux
> > package. The question is whether bison and flex both behave in a
> > reasonably similar way regardless of which version is used.
> 
>  I briefly looked at this in Paris, and it became clear very quickly that even a
> minor change in the bison version would give a completely different .c file. If
> this is a source file that will be built for the target, it's going to be a
> major reproducibility-killer. So I don't think we can remove host-bison and
> host-flex.

We're only talking about dropping the need for host-flex and host-bison
for the kconfig stuff. In this case, we don;t care that the user
generates C code one way or another: it's only a host tool...

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-05-28 20:37 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
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 [this message]
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=20180528203743.GK2965@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 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.