From: Junio C Hamano <gitster@pobox.com>
To: Robert Schiele <rschiele@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] some systems don't have (and need) sys/select.h
Date: Thu, 24 Jan 2008 13:17:14 -0800 [thread overview]
Message-ID: <7vk5ly9b51.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080124183446.GJ30676@schiele.dyndns.org> (Robert Schiele's message of "Thu, 24 Jan 2008 19:34:46 +0100")
Robert Schiele <rschiele@gmail.com> writes:
> The select stuff is already in sys/time.h on on some systems like HP-UX
> thus we should not include sys/select.h in that case.
>
> Signed-off-by: Robert Schiele <rschiele@gmail.com>
The patch looks good. I'd rather try to be a bit more helpful
to people who want to port git to their system that is not
HP-UX, though.
How about wording it like this?
Subject: pre-POSIX.1-2001 systems do not have <sys/select.h>
POSIX.1-2001 has declaration of select(2) in <sys/select.h>, but
in previous version of SUS, it is declared in <sys/time.h>,
which is already included in git-compat-util.h.
This introduces NO_SYS_SELECT_H macro in the Makefile to be set
on older systems, to skip inclusion of <sys/select.h> that does
not exist on them.
We could check _POSIX_VERSION with 200112L and do this
automatically, but earlier it was reported that the approach
does not work well on some vintage of HP-UX. Other systems may
get _POSIX_VERSION itself wrong. At least for now, this manual
configuration is safer.
next prev parent reply other threads:[~2008-01-24 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:34 [PATCH] some systems don't have (and need) sys/select.h Robert Schiele
2008-01-24 21:15 ` Johannes Schindelin
2008-01-24 21:17 ` Junio C Hamano [this message]
2008-01-24 21:58 ` Robert Schiele
2008-01-25 11:19 ` [PATCH] autoconf: Add test for sys/select.h header file Jakub Narebski
2008-01-25 12:30 ` Johannes Schindelin
2008-01-25 12:53 ` Robert Schiele
2008-01-26 6:25 ` Junio C Hamano
2008-01-26 9:42 ` Robert Schiele
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=7vk5ly9b51.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rschiele@gmail.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 NNTP newsgroup(s).