From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Assume an unrecognized gnatmake is very new
Date: Fri, 17 Jul 2026 10:37:06 -0600 [thread overview]
Message-ID: <871pd1y3m5.fsf@tromey.com> (raw)
In-Reply-To: <20260701191329.2287960-1-tromey@adacore.com> (Tom Tromey's message of "Wed, 1 Jul 2026 13:13:29 -0600")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> I don't know why -- though I suspect there may have been a change to
Tom> the output of "gnatmake --version" -- but recently some gdb.ada tests
Tom> have stopped running when llvm-gnatmake is used.
Tom> The llvm-gnatmake I am testing against prints a version string that
Tom> isn't recognized by gnat_version_compare. However, it seems to me
Tom> that AdaCore is probably the main place where this can even occur; and
Tom> furthermore that without some extra work, it seems reasonable for
Tom> gnat_version_compare to assume that an unrecognized gnatmake is "very
Tom> new".
I'm checking this in.
Tom
prev parent reply other threads:[~2026-07-17 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 19:13 Tom Tromey
2026-07-17 16:37 ` Tom Tromey [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=871pd1y3m5.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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