From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>
Cc: thuth@redhat.com, anjo@rev.ng, bcain@quicinc.com,
pbonzini@redhat.com, philmd@linaro.org, qemu-devel@nongnu.org,
qemu-trivial@nongnu.org, quic_acaggian@quicinc.com,
tsimpson@quicinc.com
Subject: Re: [PATCH] Hexagon (meson.build): define min bison version
Date: Tue, 7 Feb 2023 17:12:36 +0000 [thread overview]
Message-ID: <Y+KGhCnjqOE43SIN@redhat.com> (raw)
In-Reply-To: <20230207165603.107707-1-quic_mathbern@quicinc.com>
On Tue, Feb 07, 2023 at 01:56:03PM -0300, Matheus Tavares Bernardino wrote:
> Thomas Huth <thuth@redhat.com> wrote:
> >
> > Out of curiosity: Where did you encounter this problem? After having a quick
> > look at https://repology.org/project/bison/versions it seems to me that all
> > our supported OS distros should already ship bison 3.0 or newer...
>
> I actually noticed this when compiling our downstream
> qemu-system-hexagon on macOS (Ventura 13.2), where the bundled bison
> version is 2.3 (although 3.8.2 is available through brew). I thought
> this could affect other upstream users too, but good to know that the
> supported OSes already ship bison >= 3.0.
FWIW, our testing on macOS heavily relies on the versions from brew.
You can see the list of brew pkgs we consume in
qemu.git/.gitlab-ci.d/cirrus/macos-12.vars
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-02-07 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:52 [PATCH] Hexagon (meson.build): define min bison version Matheus Tavares Bernardino
2023-02-07 14:54 ` Philippe Mathieu-Daudé
2023-02-07 15:08 ` Thomas Huth
2023-02-07 15:49 ` Taylor Simpson
2023-02-07 16:07 ` Alessandro Di Federico
2023-02-07 16:07 ` Alessandro Di Federico via
2023-02-07 16:11 ` Philippe Mathieu-Daudé
2023-02-07 16:12 ` Philippe Mathieu-Daudé
2023-02-08 8:53 ` Bastian Koppelmann
2023-02-07 16:56 ` Matheus Tavares Bernardino
2023-02-07 17:12 ` Daniel P. Berrangé [this message]
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=Y+KGhCnjqOE43SIN@redhat.com \
--to=berrange@redhat.com \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quic_acaggian@quicinc.com \
--cc=quic_mathbern@quicinc.com \
--cc=thuth@redhat.com \
--cc=tsimpson@quicinc.com \
/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.