From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Issues with stdio.h
Date: Mon, 20 Feb 2012 23:08:00 -0000 [thread overview]
Message-ID: <4F42D251.10702@redhat.com> (raw)
In-Reply-To: <4F42CFD0.8020204@bellsouth.net>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
On 02/20/2012 03:57 PM, Robert Miles wrote:
> Why not put a stddef.h file into /user/include that includes comments
> showing
> where to find the compiler-specific stddef.h files?
Why not ask the upstream gcc list? This is not a situation specific to
Cygwin, so asking on this list won't get it changed.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-02-20 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 0:07 Chris Sutcliffe
2012-02-20 0:25 ` Christopher Faylor
2012-02-20 21:40 ` Thomas Wolff
2012-02-20 22:10 ` Eric Blake
2012-02-20 22:58 ` Thomas Wolff
2012-02-20 23:05 ` Eric Blake
2012-02-20 22:12 ` JonY
2012-02-20 22:58 ` Robert Miles
2012-02-20 23:08 ` Eric Blake [this message]
2012-02-21 1:10 ` Christopher Faylor
2012-02-21 13:01 ` Earnie Boyd
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=4F42D251.10702@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.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).