From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] common/filestuff.c: No sockets on DJGPP.
Date: Thu, 23 May 2013 18:37:00 -0000 [thread overview]
Message-ID: <519E61D2.1060207@redhat.com> (raw)
In-Reply-To: <87y5b5bllk.fsf@fleche.redhat.com>
On 05/22/2013 03:49 AM, Eli Zaretskii wrote:
> This is fine with me, thanks.
On 05/23/2013 07:24 PM, Tom Tromey wrote:
> Pedro> * common/filestuff.c [USE_WIN32API]: Define HAVE_SOCKETS.
> Pedro> [HAVE_SYS_SOCKET_H]: Define HAVE_SOCKETS.
> Pedro> (socket_mark_cloexec, gdb_socketpair_cloexec, gdb_socket_cloexec):
> Pedro> Only define if HAVE_SOCKETS is defined.
> Pedro> * configure.ac: Check for sys/socket.h.
> Pedro> * config.in, configure: Regenerate.
>
> Looks good to me. Thanks.
Thanks guys. I've put it in now.
--
Pedro Alves
prev parent reply other threads:[~2013-05-23 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 20:33 Pedro Alves
2013-05-22 2:50 ` Eli Zaretskii
2013-05-23 18:25 ` Tom Tromey
2013-05-23 18:37 ` Pedro Alves [this message]
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=519E61D2.1060207@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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