From: Andrew Cagney <ac131313@cygnus.com>
To: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: RFA: delete generated files
Date: Tue, 18 Apr 2000 21:11:00 -0000 [thread overview]
Message-ID: <38FD31AB.EA96653E@cygnus.com> (raw)
Hello,
The attatched deletes what appear to be two stray itcl files from the
repository.
Ok? It's intended for gdb-5.0 branch.
Andrew
Wed Apr 19 13:58:32 2000 Andrew Cagney <cagney@b1.cygnus.com>
* itcl/unix/config.log, itcl/unix/confdefs.h: Delete generated
files.
Index: itcl/itcl/unix/confdefs.h
===================================================================
RCS file: confdefs.h
diff -N confdefs.h
*** /sourceware/cvs-tmp/cvslQpKEd Tue Apr 18 21:02:26 2000
--- /dev/null Tue May 5 13:32:27 1998
***************
*** 1 ****
-
--- 0 ----
Index: itcl/itcl/unix/config.log
===================================================================
RCS file: config.log
diff -N config.log
*** /sourceware/cvs-tmp/cvswqoU4d Tue Apr 18 21:02:26 2000
--- /dev/null Tue May 5 13:32:27 1998
***************
*** 1,12 ****
- This file contains any messages produced by compilers while
- running configure, to aid debugging if configure makes a mistake.
-
- configure:628: checking for a BSD compatible install
- configure:681: checking for ranlib
- configure:716: checking for gcc
- configure:826: checking whether the C compiler (gcc ) works
- configure:840: gcc -o conftest conftest.c 1>&5
- configure:860: checking whether the C compiler (gcc ) is a cross-compiler
- configure:865: checking whether we are using GNU C
- configure:874: gcc -E conftest.c
- configure:893: checking whether gcc accepts -g
--- 0 ----
next reply other threads:[~2000-04-18 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 21:11 Andrew Cagney [this message]
2000-04-19 9:56 ` James Ingham
2000-04-19 10:27 ` Syd Polk
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=38FD31AB.EA96653E@cygnus.com \
--to=ac131313@cygnus.com \
--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).