From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: PATCH: PR testsuite/12040: GDB Fortran tests use g77 instead of gfortran
Date: Wed, 29 Jun 2011 14:51:00 -0000 [thread overview]
Message-ID: <BANLkTim3i2U37bBUuFryQ9g1O8QpKNNmXw@mail.gmail.com> (raw)
In-Reply-To: <m3liwk3dg9.fsf@fleche.redhat.com>
On Wed, Jun 29, 2011 at 7:43 AM, Tom Tromey <tromey@redhat.com> wrote:
> Tom> I sent a patch to dejagnu to allow f90 today; so perhaps the result
> Tom> could be based on that. I can do the work if you like, just let me
> Tom> know.
>
> H.J.> Please do.
>
> Here is what I am checking in.
>
> This moves the copied code to a new file, future.exp, and arranges to
> always load it. I refreshed one copied proc from dejagnu, with my
> gfortran patch included. I also changed how the overrides are
> installed.
>
> Tom
>
> 2011-06-29 Tom Tromey <tromey@redhat.com>
>
> PR testsuite/12040:
> * lib/future.exp: New file, mostly extracted from ada.exp.
> Rewrote compatibility code to use rename.
> (gdb_find_gfortran): New proc.
> (gdb_default_target_compile): Refresh from dejagnu; plus a pending
> gfortran patch.
> * lib/ada.exp (gdb_find_gnatmake, gdb_default_target_compile):
> Move to future.exp.
> * lib/gdb.exp: Always load future.exp.
>
Did we get gfortran when searching for F77/f77 compiler?
--
H.J.
next prev parent reply other threads:[~2011-06-29 14:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 18:24 H.J. Lu
2011-06-28 19:35 ` Tom Tromey
2011-06-28 19:56 ` H.J. Lu
2011-06-29 14:44 ` Tom Tromey
2011-06-29 14:51 ` H.J. Lu [this message]
2011-06-29 14:58 ` Tom Tromey
2011-06-29 17:50 ` Tom Tromey
2011-06-29 17:52 ` H.J. Lu
2011-06-29 18:26 ` Tom Tromey
2011-06-29 18:29 ` H.J. Lu
2011-06-30 13:29 ` Tom Tromey
2011-06-29 20:45 ` Jan Kratochvil
2011-06-29 20:49 ` Tom Tromey
2011-06-29 20:56 ` Jan Kratochvil
2011-06-29 16:10 ` Joel Brobecker
2011-06-29 17:35 ` Tom Tromey
2011-06-29 17:58 ` Joel Brobecker
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=BANLkTim3i2U37bBUuFryQ9g1O8QpKNNmXw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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