Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/stabs] weird.exp: skip hp
Date: Wed, 07 Jan 2004 21:38:00 -0000	[thread overview]
Message-ID: <16380.31751.536695.156205@localhost.redhat.com> (raw)
In-Reply-To: <20040107213133.4B8C34B35A@berman.michael-chastain.com>

Michael Elizabeth Chastain writes:
 > This patch fixes weird.exp so that it skips properly on hp-ux.
 > 
 > The old code looked at the CC environment variable.  The new code looks
 > at hp_cc_compiler and hp_aCC_compiler.
 > 
 > This isn't perfect, because we really want to test for the HP assembler,
 > not the HP compiler.  If someone is using an HP compiler then of course
 > they are using the HP assembler.  But if someone is using gcc with the
 > HP assembler (which is not recommended on hp-ux), then the test script
 > is going to execute.
 > 
 > If I detect hp_cc_compiler or hp_aCC_compiler, I issue one UNSUPPORTED
 > message and skip the test script.
 > 
 > I also fixed the copyright years by adding years where patches were
 > committed to this file on cvs HEAD.  I could do this as a separate
 > patch if you want.
 > 
 > Tested on:
 > 
 >   native i686-pc-linux-gnu, gcc 2.95.3 3.3.2 HEAD, dwarf-2 and stabs+
 >   native hppa2.0w-hp-hpux11.11, hp ansi c
 > 
 > Okay to commit?
 > 
 > Michael C
 > 
 > 2004-01-07  Michael Chastain  <mec.gnu@mindspring.com>
 > 
 > 	* gdb.stabs/weird.exp: Use hp_cc_compiler and hp_aCC_compiler
 > 	to test for hp-ux assembler.  Fix copyright years.

Ok.

elena


  reply	other threads:[~2004-01-07 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 21:31 Michael Elizabeth Chastain
2004-01-07 21:38 ` Elena Zannoni [this message]
2004-01-07 23:59 ` Andrew Cagney
2004-01-07 21:59 Michael Elizabeth Chastain
2004-01-08  0:40 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=16380.31751.536695.156205@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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