From: DJ Delorie <dj@redhat.com>
To: ian@airs.com
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: [PATCH/libiberty] Add missing <sys/types.h> in unlink-if-ordinary.c
Date: Mon, 28 Mar 2005 02:35:00 -0000 [thread overview]
Message-ID: <200503280235.j2S2Z4vS010751@greed.delorie.com> (raw)
In-Reply-To: <m3ll88wlz5.fsf@gossamer.airs.com> (message from Ian Lance Taylor on 27 Mar 2005 21:19:42 -0500)
> <sys/types.h> is not an ISO C header file. But it is in POSIX.1.
> And it is available on every Unix system. Because of that, it is
> available on every Unix workalike system.
Right, but the machines that wouldn't have it, probably would have K&R
compilers anyway. We haven't had a problem using it unprotected so
far, and there's even less reason to worry about it now.
next prev parent reply other threads:[~2005-03-28 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 14:21 Mark Kettenis
2005-03-26 14:27 ` Andrew Haley
2005-03-26 14:38 ` Mark Kettenis
2005-03-28 2:08 ` DJ Delorie
2005-03-28 2:19 ` Ian Lance Taylor
2005-03-28 2:35 ` DJ Delorie [this message]
2005-03-28 14:43 ` Mark Kettenis
2005-03-28 17:17 ` DJ Delorie
2005-03-27 18:48 ` Ian Lance Taylor
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=200503280235.j2S2Z4vS010751@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.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).