From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Tom Tromey <tom@tromey.com>,
Torbjorn SVENSSON via Gdb <gdb@sourceware.org>
Subject: Re: GDB13 fails to build on MacOS using supplied GNU Bison 2.3
Date: Thu, 31 Aug 2023 16:01:34 +0200 [thread overview]
Message-ID: <0007c884-16a1-2fe3-e574-d9fe5c944c83@foss.st.com> (raw)
In-Reply-To: <87jztbpccn.fsf@tromey.com>
Hello Tom,
On 2023-08-31 15:31, Tom Tromey wrote:
>>>>>> "Torbjorn" == Torbjorn SVENSSON via Gdb <gdb@sourceware.org> writes:
>
> Torbjorn> All three versions of MacOS includes GNU Bison 2.3 and it appears that
> Torbjorn> this issue was fixed in GNU Bison 2.4.
>
> If the appended works for you (be sure to run some tests), I can check
> it in.
Not sure what you mean by "appended" here... I see no attachment and my
mail clarily stated that I could not generate the configure script using
the autotools.
> Torbjorn> Looking at the binutils tree, I see that sub-directory gprofng
> Torbjorn> contains bison.m4 and a check to confirm that at least version 3.0.4
> Torbjorn> is available.
>
> Torbjorn> I think the bison.m4 file should be moved up one level and used in
> Torbjorn> both gprofng and gdb, but I'm unable to re-generate the configure
> Torbjorn> scripts.
>
> I wonder if this would really help you, since presumably it would just
> reject your bison?
Well, what I was thinking was to have something telling the user that
the sources requires version x.y of bison rather than silently breaking
during the compile stage with some obscure error message.
> Another option might be to install bison from brew. In this case it's
> probably fine but eventually we may want to require a newer Bison, and
> IMO we can't and shouldn't keep catering to Apple's problem
> indefinitely.
Yes, this is how I solved it on out system, but it's still not as
helpful as a configure error would have been to let others know that the
bison version is too old...
Regards,
Torbjörn
next prev parent reply other threads:[~2023-08-31 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 18:11 Torbjorn SVENSSON
2023-08-28 5:12 ` Tom de Vries
2023-08-31 13:31 ` Tom Tromey
2023-08-31 14:01 ` Torbjorn SVENSSON [this message]
2023-08-31 18:44 ` Tom Tromey
2023-09-01 10:51 ` Martin Simmons
2023-09-01 13:02 ` Tom Tromey
2023-09-14 20:26 ` Torbjorn SVENSSON
2023-09-14 21:32 ` Tom Tromey
2023-09-15 12:04 ` Torbjorn SVENSSON
2023-09-17 1:21 ` Tom Tromey
2023-09-17 15:26 ` Torbjorn SVENSSON
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=0007c884-16a1-2fe3-e574-d9fe5c944c83@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=gdb@sourceware.org \
--cc=tom@tromey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).