Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch 1/2] mingw: update gnulib: prepare the sources
Date: Mon, 23 Mar 2015 19:28:00 -0000	[thread overview]
Message-ID: <55106949.7090602@redhat.com> (raw)
In-Reply-To: <20150323191753.GB7142@calimero.vinschen.de>

On 03/23/2015 07:17 PM, Corinna Vinschen wrote:
> On Mar 23 16:51, Pedro Alves wrote:
>> Hi guys,
>>
>> We really need to move forward with importing a newer gnulib,
>> for several reasons...
> 
> I'm not quite sure why I'm CCed on this thread, 

Dunno, I just hit reply to all.

> but please keep in mind
> that Cygwin tries hard to be a POSIX platform.  Please, don't mix Windows
> headers and Windows calls in, unless you really, *really* need them.
> 
> Especially don't mix in winsock headers and the definitions of timeval,
> they collide with the POSIX definitions in the newlib headers.

Yep, don't worry, that's not being proposed.  Even Jan's original patch
limited the windows.h inclusion to mingw.  If a gnulib header ends up
pulling windows.h on Cygwin, that'd be a gnulib bug.  I think the chances
of that happening without the gnulib folks noticing are quite low
though.

But the best way to make sure is to test the users/palves/gnulib-update branch.  :-)

Thanks,
Pedro Alves


  reply	other threads:[~2015-03-23 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 22:12 Jan Kratochvil
2014-12-23 11:54 ` Kai Tietz
2014-12-24 22:20   ` Jan Kratochvil
2015-03-23 16:51     ` Pedro Alves
2015-03-23 17:08       ` Jan Kratochvil
2015-03-23 17:25         ` Pedro Alves
2015-03-23 17:32           ` Jan Kratochvil
2015-03-23 17:37           ` Eli Zaretskii
2015-03-23 17:57             ` Pedro Alves
2015-08-24 18:09               ` Pedro Alves
2015-03-23 19:17       ` Corinna Vinschen
2015-03-23 19:28         ` Pedro Alves [this message]
2015-03-23 19:47           ` Corinna Vinschen

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=55106949.7090602@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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