public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: insight@sourceware.cygnus.com
Subject: make check in itcl
Date: Sat, 29 Apr 2000 07:21:00 -0000	[thread overview]
Message-ID: <u84s8l7zv6.fsf@gromit.rhein-neckar.de> (raw)

Running make check with the whole sourceware tree checked out results
in:

make[1]: Leaving directory `/usr/src/build-gdb/intl'
make[1]: Entering directory `/usr/src/build-gdb/itcl'
make[1]: *** No rule to make target `check'.

We should ignore check in itcl.  Please apply the appended patch.

Andreas

2000-04-29  Andreas Jaeger  <aj@suse.de>

	* Makefile.in (check): Add rule to ignore make check.

Index: itcl/Makefile.in
===================================================================
RCS file: /cvs/src/src/itcl/Makefile.in,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 Makefile.in
--- Makefile.in	2000/02/07 00:19:46	1.1.1.1
+++ Makefile.in	2000/04/29 14:20:10
@@ -70,7 +70,7 @@
 		then true; else exit 1; fi \
 	done;
 
-install-info info install-check:
+install-info info install-check check:
 
 clean:
 	for dir in $(subdirs) ; do \

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.rhein-neckar.de

             reply	other threads:[~2000-04-29  7:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Syd>
     [not found] ` <Polk's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Wed,>
     [not found]       ` <"Tue,>
     [not found]       ` <"28>
     [not found]       ` <"Mon,>
     [not found]         ` <01>
     [not found]           ` <May>
     [not found]             ` <2000>
     [not found]               ` <09:07:18>
     [not found]                 ` <-0700>
2000-04-29  7:21                   ` Andreas Jaeger [this message]
2000-05-01  9:05                     ` Syd Polk
2000-05-01  9:27                       ` Andreas Jaeger
2000-05-01 10:15                         ` Syd Polk
2000-05-01 10:58                           ` Andreas Jaeger
2000-05-01 11:21                             ` Syd Polk
2000-05-03 10:37                             ` Syd Polk
2000-05-03 12:05                               ` Andreas Jaeger
2000-05-03 12:37                                 ` Syd Polk
2000-05-04  2:34                                   ` Andrew Cagney
     [not found]               ` <09:17:35>
     [not found]                 ` <-0800>
2000-11-21 16:03                   ` rename to insight Tom Tromey
     [not found]                     ` <mailpost.974851789.4627@postal.sibyte.com>
2000-11-22  9:42                       ` Chris G. Demetriou
2000-11-22 10:29                         ` Tom Tromey
2000-11-28  9:18                           ` Chris G. Demetriou
2000-11-28  9:34                             ` Tom Tromey
2000-11-28 12:52                               ` Syd Polk
2000-11-28 10:34 Patch: fixlet in gdbtk-cmds.c Tom Tromey
2000-11-28 12:55 ` Syd Polk
2000-11-28 13:46   ` Tom Tromey
2000-11-28 14:47     ` Syd Polk
2000-11-28 17:32   ` Tom Tromey
2000-11-28 23:51     ` Syd Polk
2000-11-29 13:48       ` Tom Tromey
2000-11-29 18:41         ` Syd Polk
2000-11-29 20:07           ` Fernando Nasser
2000-11-30  9:09             ` Tom Tromey
2000-11-30  9:57               ` Fernando Nasser

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=u84s8l7zv6.fsf@gromit.rhein-neckar.de \
    --to=aj@suse.de \
    --cc=insight@sourceware.cygnus.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).