From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc/testsuite/fortran] add fortran programs
Date: Tue, 17 Aug 2004 16:41:00 -0000 [thread overview]
Message-ID: <41223533.nail4ZR16TCLE@mindspring.com> (raw)
In-Reply-To: <411F2121.nailA3X1XNYD7@mindspring.com>
Committed.
Tested on native i686-pc-linux-gnu.
But I missed the key spot in Makefile.in. So it's not actually hooked
up yet. :( Another patch coming when I get some more cycles.
===
2004-08-17 Michael Chastain <mec.gnu@mindspring.com>
* configure.in: Add gdb.fortran.
* configure: Regenerate.
* gdb.fortran/Makefile.in: New file.
* lib/gdb.exp (skip_fortran_tests): New procedure.
prev parent reply other threads:[~2004-08-17 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 8:39 Michael Chastain
2004-08-17 16:41 ` Michael Chastain [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=41223533.nail4ZR16TCLE@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@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