From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Issues with stdio.h
Date: Mon, 20 Feb 2012 23:05:00 -0000 [thread overview]
Message-ID: <4F42D1A8.7000808@redhat.com> (raw)
In-Reply-To: <4F42CFFD.2040403@towo.net>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On 02/20/2012 03:58 PM, Thomas Wolff wrote:
>> Wrong. GNU/Linux does this too. On my Fedora machine,
>>
>> $ printf '#include<stddef.h>\n#include<stdio.h>\n' | gcc -E -\
>> |grep '^# 1 "/'
...
>> # 1 "/usr/lib/gcc/x86_64-redhat-linux/4.6.2/include/stddef.h" 1 3 4
>> # 1 "/usr/include/wchar.h" 1 3 4
>> # 1 "/usr/lib/gcc/x86_64-redhat-linux/4.6.2/include/stdarg.h" 1 3 4
>
> As I interpret this, stddef.h - containing those constants - is the only
> file with this setup, so be it.
Reading the trace I posted above, it is not just <stddef.h>, but also at
least <stdarg.h>, and probably others, too.
> (I had actually checked on a SunOS system.)
SunOS isn't GNU/Linux, so it is less relevant to how cygwin behaves
(since cygwin is striving to be a Linux emulation, not a POSIX
emulation). Not to mention that using gcc on SunOS _also_ prefers to
translate <stddef.h> to a gcc-specific directory, rather than
/usr/include/stddef.h, since gcc relies on aspects that are specific to
the gcc compiler, while /usr/include/stddef.h is tied to the system's
own 'cc' that doesn't understand gcc extensions.
--
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:05 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 [this message]
2012-02-20 22:12 ` JonY
2012-02-20 22:58 ` Robert Miles
2012-02-20 23:08 ` Eric Blake
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=4F42D1A8.7000808@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).