public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
	Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	gcc@gcc.gnu.org
Subject: Re: Problems with "make check"
Date: Thu, 03 Apr 2003 19:11:00 -0000	[thread overview]
Message-ID: <8765pvr1il.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20030403071804.GA22578@disaster.jaj.com>

>>>>> "Phil" == Phil Edwards <phil@jaj.com> writes:

Phil> You're not the first.  :-) It would require a one-line change to
Phil> automake's $share/am/dejagnu.am, and I'm not sure what else.

That should be it.  However, that's automake 1.4.  I doubt the current
maintainer would want to do another 1.4.x release.  libgcj already has
a mini-fork though; you could put it there.

The code in there is a little weird in another way:

	runtest=$(RUNTEST); \
## If runtest can't be found, print a warning but don't die.  It is
## pointless to cause a failure if the tests cannot be run at all.
	if $(SHELL) -c "$$runtest --version" > /dev/null 2>&1; then \
	  l='$(DEJATOOL)'; for tool in $$l; do \
	    $$runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS) $(RUNTESTFLAGS); \
	  done; \
	else echo "WARNING: could not find \`runtest'" 1>&2; :;\

This seems backwards now.  I mean, wouldn't you want a failure if you
can't run the tests?  So that you know they didn't get run?

Some of this older code just copied existing practice, though,
independent of whether said practice made sense.

Tom

  parent reply	other threads:[~2003-04-03 16:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28  8:47 Richard Kenner
2003-04-02 22:25 ` Zack Weinberg
2003-04-03  6:18   ` Andreas Jaeger
2003-04-03  6:24     ` Zack Weinberg
2003-04-03  6:32       ` Andreas Jaeger
2003-04-03  8:30         ` Phil Edwards
2003-04-03 11:30           ` Andreas Schwab
2003-04-03 11:49             ` Gerald Pfeifer
2003-04-03 19:26               ` Mike Stump
2003-04-03 19:11           ` Tom Tromey [this message]
2003-04-03 20:19             ` Phil Edwards
2003-04-02 22:47 Richard Kenner
2003-04-03 13:02 Richard Kenner
2003-04-03 14:04 ` Andreas Jaeger

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=8765pvr1il.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=phil@jaj.com \
    --cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).