From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>, Indu Bhagat <indu.bhagat@oracle.com>
Cc: binutils@sourceware.org
Subject: Re: Question regarding min reqd dejagnu version
Date: Tue, 4 Oct 2022 12:40:22 +0100 [thread overview]
Message-ID: <eb00e7ef-94bd-e03b-fa31-2376e566cba8@redhat.com> (raw)
In-Reply-To: <64b96645-bf9f-cd77-940a-6b8424491961@suse.com>
Hi Indu,
On 10/4/22 11:27, Jan Beulich wrote:
>> Do you have a suggestion for a better minimum version, or do
>> you think that instead tests that do require newer versions of dejagnu
>> should check for that before they run ?
>
> I think checking for features before use would be the preferred way to go.
Would that work for you ? Ie could you test for a minimum dejangu version
before attempting to compile your test source files ?
Cheers
Nick
next prev parent reply other threads:[~2022-10-04 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 0:18 Indu Bhagat
2022-10-03 10:23 ` Nick Clifton
2022-10-03 17:55 ` Indu Bhagat
2022-10-04 9:52 ` Nick Clifton
2022-10-04 10:05 ` Jan Beulich
2022-10-04 10:20 ` Nick Clifton
2022-10-04 10:27 ` Jan Beulich
2022-10-04 11:40 ` Nick Clifton [this message]
2022-10-05 18:28 ` Indu Bhagat
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=eb00e7ef-94bd-e03b-fa31-2376e566cba8@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=jbeulich@suse.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).