zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Cc: Cyril Brulebois <kibi@debian.org>
Subject: Re: PATCH: _GNU_SOURCE when __GNU__
Date: Sun, 12 Jul 2009 18:18:07 +0100	[thread overview]
Message-ID: <20090712181807.282a534a@pws-pc> (raw)
In-Reply-To: <20090712163708.GA10163@scru.org>

On Sun, 12 Jul 2009 16:37:08 +0000
Clint Adams <clint@zsh.org> wrote:

> On Sat, May 30, 2009 at 05:53:33PM +0000, Clint Adams wrote:
> > As far as I can tell, nothing is included up to this point which
> > define __GLIBC__, so the Hurd wasn't getting the
> > nanosecond-resolution structs guarded by __USE_MISC
> > and thus was not able to use them in Src/cond.c.
> > This has nothing to do with /dev/ptmx.
> 
> So it seems that Debian GNU/kFreeBSD is actually hard-coding
> a __GLIBC__ define in gcc for some reason.  Could someone
> think of a sane configure test for these struct members instead,
> or is it futile?

It should be just a question of #include'ing <sys/stat.h> and testing if
either st_atim.tv_nsec or st_atimensec is present in struct
stat---however, you'd need to be sure the definitions aren't trodden on
by something in system.h.  We really need to be sure of that anyway, to
ensure consistency, but actually system.h is a bit murky (and I mean a
bit murky on the zsh scale, not on the scale of good programming).

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


  reply	other threads:[~2009-07-12 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 17:53 Clint Adams
2009-07-12 16:37 ` Clint Adams
2009-07-12 17:18   ` Peter Stephenson [this message]
2009-08-01  4:16     ` Clint Adams

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=20090712181807.282a534a@pws-pc \
    --to=p.w.stephenson@ntlworld.com \
    --cc=kibi@debian.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).