From: Daniel Jacobowitz <drow@false.org>
To: "Doug Kwan (關振德)" <dougkwan@google.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
Michael Snyder <msnyder@specifix.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH][gdbserver] Check for sys/dir.h and sys.user.h in configuration.
Date: Fri, 25 Jul 2008 21:42:00 -0000 [thread overview]
Message-ID: <20080725214142.GA18480@caradoc.them.org> (raw)
In-Reply-To: <498552560807231014q317b59bai907c4cf9f9009f6e@mail.gmail.com>
On Wed, Jul 23, 2008 at 10:14:52AM -0700, Doug Kwan (鿝德) wrote:
> I used the autoconf-2.59.tar.bz2 from ftp.gnu.org. I got fewer spurios
> diffs than before but there still seems to be some left. Here is an
> updated patch.
>
> -Doug
>
> 2008-07-23 Doug Kwan <dougkwan@google.com>
>
> * configure.ac: Check for sys/dir.h and sys.user.h.
> * config.in configure: Regenerate.
> * linux-low.c: Include <sys/dir.h> if HAVE_SYS_DIR_H is defined.
> Include <sys/user.h> if HAVE_SYS_USER_H is defined.
> (linux_write_memory): Remove declaration of errno.
Just one question: if removing sys/user.h and sys/dir.h doesn't break
anything on android, does it break anything on other GNU/Linux
targets?
Removing the errno declaration is fine. Removing the includes is fine
if they're not actually necessary, otherwise this patch is OK.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-25 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 1:00 Doug Kwan (關振德)
2008-07-23 3:49 ` Michael Snyder
2008-07-23 8:29 ` Doug Kwan (關振德)
2008-07-23 14:15 ` Thiago Jung Bauermann
2008-07-23 14:33 ` Daniel Jacobowitz
2008-07-23 17:15 ` Doug Kwan (關振德)
2008-07-25 21:42 ` Daniel Jacobowitz [this message]
2008-07-25 22:54 ` Doug Kwan (關振德)
2008-07-25 23:02 ` Doug Kwan (關振德)
2008-07-25 21:35 ` Doug Kwan (關振德)
2008-07-23 7:57 ` Andreas Schwab
2008-07-23 8:33 ` Doug Kwan (關振德)
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=20080725214142.GA18480@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=dougkwan@google.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.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