From: Ben Elliston <bje@wasabisystems.com>
To: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: DejaGnu 1.4.4 release
Date: Fri, 30 Jan 2004 10:54:00 -0000 [thread overview]
Message-ID: <87smhxiu5d.fsf@wasabisystems.com> (raw)
DejaGnu 1.4.4 has been released.
This release cleans up the source tree, makes a start at overhauling
the documentation, updates to modern versions of build tools like
automake and autoconf and applies patches that have been accumulating
in the sibling source repository at sources.redhat.com.
The hope is that these cleanups will make it easier to start improving
DejaGnu on a wider scale. Feel free to submit suggestions to the
DejaGnu mailing list for improvements.
Major changes from 1.4.2 and 1.4.3:
1. New XML output option, so test results can be loaded into a database.
2. Support for the KFAIL/KPASS (known failures).
3. New "Hello World" example.
4. New tutorial chapter.
5. Test cases build with either GCC 2.x or 3.x.
6. BlueGnu has been removed from the contrib directory.
7. The contrib/test* scipts were bitrotten and have been removed. If
you still want copies of these, they can be found in the previous
DejaGnu release.
8. i960glue.c has been removed.
The source tar file is now available from:
ftp.gnu.org:/pub/gnu/dejagnu/dejagnu-1.4.4.tar.gz
The MD5 checksum of the file is:
MD5 (dejagnu-1.4.4.tar.gz) = 053f18fd5d00873de365413cab17a666
Enjoy!
next reply other threads:[~2004-01-30 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 10:54 Ben Elliston [this message]
2004-02-05 19:34 ` Andrew Cagney
2004-02-05 20:38 ` Ben Elliston
2004-02-05 20:50 ` Gerald Pfeifer
2004-02-05 23:01 ` Joe Buck
2004-02-01 2:02 Michael Elizabeth Chastain
2004-02-05 23:21 Michael Elizabeth Chastain
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=87smhxiu5d.fsf@wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.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