From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: more robust get_compiler_info
Date: Thu, 05 Feb 2004 22:53:00 -0000 [thread overview]
Message-ID: <20040205225333.9B2014B364@berman.michael-chastain.com> (raw)
drow> Not sure how much it matters but... the variable is hp_aCC_compiler, I
drow> believe.
Urgl, right you are.
Michael C
next reply other threads:[~2004-02-05 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 22:53 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 23:13 Michael Elizabeth Chastain
2004-02-06 18:33 ` Andrew Cagney
2004-02-07 3:02 ` Joel Brobecker
2004-02-05 12:34 Michael Elizabeth Chastain
2004-02-05 15:03 ` Daniel Jacobowitz
2004-02-05 15:26 ` Andrew Cagney
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=20040205225333.9B2014B364@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=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