From: "Ramsay Jones" <ramsay@ramsay1.demon.co.uk>
To: "Junio C Hamano" <junkio@cox.net>
Cc: <git@vger.kernel.org>
Subject: RE: [PATCH 6/10] Fix header breakage with _XOPEN_SOURCE.
Date: Wed, 2 Aug 2006 19:47:51 +0100 [thread overview]
Message-ID: <001d01c6b664$285ff540$c47eedc1@ramsay1.demon.co.uk> (raw)
In-Reply-To: <7vpsfjvaul.fsf@assigned-by-dhcp.cox.net>
On Wed, 2006-08-02 at 8:46, Junio C Hamano wrote:
>
> "Ramsay Jones" <ramsay@ramsay1.demon.co.uk> writes:
>
> > convert-objects.c sets _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED before
> > including <time.h>, in order to get the declaration of strptime().
> > This leads to breakage in cache.h, due to S_ISLNK and S_IFLNK no longer
> > being defined by <sys/stat.h>. These definitions are protected by the
> > __USE_BSD symbol, which is not set when _XOPEN_SOURCE is set. Moving
> > the #defines and #include <time.h> below all other #includes does not
> > fix the problem, however, since now _USE_XOPEN, which protects the
> > declaration of strptime(), is now not defined (don't ask!).
>
> Wouldn't including "cache.h" and friends first and including
> <time.h> last solve the problem, then?
>
Not for me. It may be a glibc 2.1 specific problem, of course, but
strptime() remains undeclared.
> This kind of change tends to fix one system while potentially
> breaking another, and we would need to be careful. Will queue
> for post 1.4.2 and have people scream if it breaks somebody, I
> guess.
>
Yes, I had some concern about that myself. Unfortunately, you can't
make it conditional on the glibc version macros; in order to get the
macros, you have to include (one way or another) <features.h>, at which
point it is already too late ...
Ramsay
next prev parent reply other threads:[~2006-08-02 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 1:03 [PATCH 6/10] Fix header breakage with _XOPEN_SOURCE Ramsay Jones
2006-08-02 7:46 ` Junio C Hamano
2006-08-02 18:47 ` Ramsay Jones [this message]
2006-08-04 0:19 ` Johannes Schindelin
2006-08-05 17:11 ` Ramsay Jones
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='001d01c6b664$285ff540$c47eedc1@ramsay1.demon.co.uk' \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).