From: prj@po.cwru.edu (Paul Jarc)
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: dewar@gnat.com, gcc@gcc.gnu.org
Subject: Re: improving testing scheme (was Re: ACATS and GCC testsuite)
Date: Tue, 01 Apr 2003 23:53:00 -0000 [thread overview]
Message-ID: <m3vfxxyffk.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <10303291407.AA03222@vlsi1.ultra.nyu.edu> (kenner@vlsi1.ultra.nyu.edu's message of "Sat, 29 Mar 03 09:07:55 EST")
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) wrote:
> The risk, in my opinion, of changing "make check" to use the compiler in
> PATH, rather than in the build directory, is that a lot of people are going
> to accidentally run the check on the wrong compiler.
"make check" could look at the configuration in the build directory to
find out where the compiler should have been installed, and look there
rather than in $PATH.
paul
next prev parent reply other threads:[~2003-04-01 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 16:43 Richard Kenner
2003-04-01 23:53 ` Paul Jarc [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 0:08 Richard Kenner
2003-04-02 0:26 ` Paul Jarc
2003-03-29 15:51 Robert Dewar
2003-03-29 15:11 Richard Kenner
2003-03-29 2:58 Nathanael Nerode
2003-03-29 12:25 ` Laurent Guerby
2003-04-02 7:49 ` Paul Jarc
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=m3vfxxyffk.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).