From: Andrew Cagney <ac131313@cygnus.com>
To: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: For review: Do not include <unistd.h>
Date: Mon, 30 Aug 1999 01:56:00 -0000 [thread overview]
Message-ID: <37CA471B.8FFEECE@cygnus.com> (raw)
FYI,
This patch matches a corresponding change to defs.h which is now
#include'ing <unistd.h>.
ok?
Andrew
Mon Aug 30 17:56:28 1999 Andrew Cagney <cagney@b1.cygnus.com>
* gdbtk.c, gdbtk-hooks.c, gdbtk-cmds.c: #include <unistd.h>
moved
to defs.h.
Index: gdbtk.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/gdbtk.c,v
retrieving revision 2.139
diff -p -r2.139 gdbtk.c
*** gdbtk.c 1999/08/28 01:30:08 2.139
--- gdbtk.c 1999/08/30 08:52:54
***************
*** 48,54 ****
#include <signal.h>
#include <fcntl.h>
- #include <unistd.h>
#include "top.h"
#include <sys/ioctl.h>
#include "gdb_string.h"
--- 48,53 ----
Index: gdbtk-hooks.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/gdbtk-hooks.c,v
retrieving revision 2.27
diff -p -r2.27 gdbtk-hooks.c
*** gdbtk-hooks.c 1999/08/07 01:27:45 2.27
--- gdbtk-hooks.c 1999/08/30 08:52:54
***************
*** 49,55 ****
#include <stdarg.h>
#include <signal.h>
#include <fcntl.h>
- #include <unistd.h>
#include "top.h"
#include <sys/ioctl.h>
#include "gdb_string.h"
--- 49,54 ----
Index: gdbtk-cmds.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/gdbtk-cmds.c,v
retrieving revision 2.56
diff -p -r2.56 gdbtk-cmds.c
*** gdbtk-cmds.c 1999/08/28 01:30:09 2.56
--- gdbtk-cmds.c 1999/08/30 08:53:01
***************
*** 47,53 ****
#include <signal.h>
#include <fcntl.h>
- #include <unistd.h>
#include "top.h"
#include <sys/ioctl.h>
#include "gdb_string.h"
--- 47,52 ----
reply other threads:[~1999-08-30 1:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=37CA471B.8FFEECE@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).