From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Check for unistd.h in gdbserver/configure.in
Date: Wed, 24 Jul 2002 14:41:00 -0000 [thread overview]
Message-ID: <1020724213418.ZM5932@localhost.localdomain> (raw)
I was seeing some warnings while building gdbreplay.o which were due
to the fact that unistd.h was not being included. I've just committed
the (hopefully obvious) change below.
* configure.in (unistd.h): Add to AC_CHECK_HEADERS list.
* configure: Regenerate.
* config.in: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/configure.in,v
retrieving revision 1.10
diff -u -p -r1.10 configure.in
--- configure.in 11 Jun 2002 17:32:39 -0000 1.10
+++ configure.in 24 Jul 2002 21:26:30 -0000
@@ -31,7 +31,7 @@ AC_PROG_INSTALL
AC_HEADER_STDC
AC_CHECK_HEADERS(sgtty.h termio.h termios.h sys/reg.h string.h dnl
- proc_service.h sys/procfs.h thread_db.h linux/elf.h)
+ proc_service.h sys/procfs.h thread_db.h linux/elf.h unistd.h)
. ${srcdir}/configure.srv
next reply other threads:[~2002-07-24 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 14:41 Kevin Buettner [this message]
2002-07-24 14:53 ` Daniel Jacobowitz
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=1020724213418.ZM5932@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.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