From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openntpd: needs host-bison
Date: Mon, 16 Nov 2020 18:42:20 +0100 [thread overview]
Message-ID: <875z655hc3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <878sb1qle4.fsf@tarshish> (Baruch Siach's message of "Mon, 16 Nov 2020 19:09:07 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Hi,
>> > +OPENNTPD_DEPENDENCIES = host-bison
>>
>> Can we not use $(BR2_BISON_HOST_DEPENDENCY) instead?
> We surly can. But for some reason no other package under package/ uses
> BR2_BISON_HOST_DEPENDENCY. Plain host-bison is used there instead. Only
> Barebox, U-Boot and the kernel use it. Why is that?
Your tree is not uptodate, we also have it in linux-backports ;)
But yes, it is a bit odd that we are not using it more often. Probably
it is mostly just because it is fairly new (~2 years) and not really
documented anywhere.
Yann, you added it, anything to add?
> Commit b01100cc901a83 ("linux: kconfig may need host-{flex, bison} to
> build the configurators") mentions kconfig. Is that related?
> I guess that BR2_BISON_HOST_DEPENDENCY is more susceptible to
> incompatibility due to different host installed bison versions (and same
> for flex).
Correct, similar to the other components where we can use what is
available on the host if new enough. For bison/flex, I would imagine
that the version incompatibilities are fairly small (even though we do
have some patches for building with bison 3.7.1).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-11-16 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 11:18 [Buildroot] [PATCH] package/openntpd: needs host-bison Baruch Siach
2020-11-16 16:19 ` Peter Korsgaard
2020-11-16 17:09 ` Baruch Siach
2020-11-16 17:42 ` Peter Korsgaard [this message]
2020-11-16 18:07 ` Yann E. MORIN
2020-11-16 18:54 ` Peter Korsgaard
2020-11-16 21:25 ` Peter Korsgaard
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=875z655hc3.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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