This is the mail archive of the
mailing list for the GCC project.
Re: PATCH to run only test where appropriate
- To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
- Subject: Re: PATCH to run only test where appropriate
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 29 Sep 1998 10:34:06 -0600
- cc: egcs-patches at cygnus dot com, burley at gnu dot org, jbuck at synopsys dot com, pfeifer at dbai dot tuwien dot ac dot at, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <13840.60777.577076.232891@slsvhmt>you write:
> On Tue, 29 September 1998, 15:53:53, firstname.lastname@example.org wrote:
> > Another thing which should be fixed: currently "make check" ignores
> > any definition of LANGUAGES; on my Motorola machines I restrict them
> > to "c c++" due to the slow machines. Unfortunately, the "check-..."
> > targets don't consider if they actually can do anything useful,
> > e.g. if "cc1plus" doesn't exist, don't even try to start "runtest"; in
> > my example, the check-f77 causes me one additional *hour* of checking
> > on the dog slow m68k box :-( I'll be sending a patch for this, too.
> This patch
> - adds code to check if the compiler to be tested even exists,
> - eliminates the redundancy of having a separate "check-" target
> for each compiler; they actually only differ in the `--tool'
> OK to install?
No. In the absence of binaries for the compiler in the build directory the
testsuite should use the compilers from the install tree. Your patch would
disable that behavior as far as I can tell.