From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PING2/rfa/testsuite] compiler.exp: rewrite get_compiler_info
Date: Sat, 24 Jan 2004 14:49:00 -0000 [thread overview]
Message-ID: <20040124144921.GA21301@nevyn.them.org> (raw)
In-Reply-To: <20040124072516.E41F44B363@berman.michael-chastain.com>
On Sat, Jan 24, 2004 at 02:25:16AM -0500, Michael Chastain wrote:
> Okay to commit?
Go ahead. I'm still not thrilled about the messing with log_file but
we can sort it out another day.
>
> Michael C
>
> 2004-01-06 Michael Chastain <mec.gnu@mindspring.com>
>
> * lib/compiler.c: Add hp_cc_compiler and hp_aCC_compiler.
> * lib/compiler.cc: Likewise.
> * lib/gdb.exp (get_compiler_info): Always call gdb_compile to
> get the right preprocessor. Eval the output directly. Remove
> special tests for hp_cc_compiler and hp_aCC_compiler. Remove
> hp_f77_compiler and hp_f90_compiler completely.
> (gdb_preprocess): Delete.
> (get_compiler): Delete.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-24 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 7:25 Michael Elizabeth Chastain
2004-01-24 14:49 ` Daniel Jacobowitz [this message]
2004-01-24 22:02 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=20040124144921.GA21301@nevyn.them.org \
--to=drow@mvista.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