From: Indu Bhagat <indu.bhagat@oracle.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: Question regarding min reqd dejagnu version
Date: Mon, 3 Oct 2022 10:55:31 -0700 [thread overview]
Message-ID: <41d734aa-50bb-2868-0ed4-e40941b5776d@oracle.com> (raw)
In-Reply-To: <d3042508-1703-ad7b-11ee-2b99c53190ee@redhat.com>
On 10/3/22 03:23, Nick Clifton wrote:
> Hi Indu,
>
>> I am wondering what should be the expectation here. Is there a minimum
>> version of dejagnu that can be expected from the users ?
>
> At the moment, no. There nearest thing that I could find was this text in
> gdb/README:
>
> Running the testsuite requires the prior installation of DejaGNU,
> which is generally available via ftp. The directory
> ftp://sources.redhat.com/pub/dejagnu/ will contain a recent snapshot.
>
> There is a function to test for dejagnu.h in config/acinclude.m4, but as
> far as I can tell it is never used.
>
> Based upon what you have discovered I would guess that a minimum of
> Dejagnu 1.5.3 is required, do you agree ? (I was going to suggest 1.5.2
> but it appears that the 1.5.3 release came out a month later, which
> suggests that it was issued in order to fix an important bug).
>
You're right - with dejagnu 1.5.2, libsframe testsuite works well. The
specific commit that fixes this issue should be:
ad36659 Steve Ellcey 2014-10-24 * dejagnu.h (pass): Make function
static as well as inline.
From the release notes, the following two commits which made to 1.5.3
seem relevant (perhaps especially the first one) -
5256bd8 H.J. Lu 2015-02-26 * lib/target.exp (default_target_compile):
Prepend multilib_flags, instead of appending it.
3249854 Stephen Tridgell 2015-02-18 * lib/framework.exp (log_and_exit):
Set tool to "testrun" if unset.
Thanks
> Cheers
> Nick
>
next prev parent reply other threads:[~2022-10-03 17:55 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 [this message]
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
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=41d734aa-50bb-2868-0ed4-e40941b5776d@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).