From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21020@debbugs.gnu.org, wgg2@member.fsf.org
Subject: bug#21020: 24.4; `display-time-world' tampers with TZ
Date: Mon, 27 Jul 2015 08:02:53 -0700 [thread overview]
Message-ID: <55B6481D.4080208@cs.ucla.edu> (raw)
In-Reply-To: <83fv49zsuq.fsf@gnu.org>
Eli Zaretskii wrote:
> I needed the changes in 7009674 to get this to build cleanly on
> MinGW. One of the changes in that commit is in lib/time.in.h.
Thanks, I ported that code fix back to gnulib, as gnulib master commit
b18e6d98e211be6bb0e720952a9baef7da1d27cb.
> It sounds like similar changes are needed in other Gnulib headers,
> lest they produce similar problems at some point. I can provide a
> list of all the __need_SOMETHING symbols used by the MinGW headers, if
> that will help.
I looked into that and came up with the following list:
__need_NULL
__need_ptrdiff_t
__need_size_t
__need_struct_timespec
__need_time_t
__need___va_list
__need_wchar_t
__need_wint_t
The only other Gnulib header that refers to any of these symbols is stddef.in.h
and if it's not used in MinGW then I expect we don't need to worry about it.
Though there may be issues in MinGW itself, if it's using these symbols
incompatibly with what GCC expects (stddef.h is a GCC header).
next prev parent reply other threads:[~2015-07-27 15:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 19:39 bug#21020: 24.4; `display-time-world' tampers with TZ William G. Gardella
2015-07-26 7:09 ` Paul Eggert
2015-07-26 14:48 ` Eli Zaretskii
2015-07-26 17:05 ` Paul Eggert
2015-07-26 17:34 ` Eli Zaretskii
2015-07-26 17:37 ` Eli Zaretskii
2015-07-26 17:55 ` Paul Eggert
2015-07-26 18:21 ` Eli Zaretskii
2015-07-26 19:48 ` Paul Eggert
2015-07-27 12:29 ` Eli Zaretskii
2015-07-27 15:02 ` Paul Eggert [this message]
2015-07-27 15:22 ` Eli Zaretskii
2015-07-27 15:38 ` Eli Zaretskii
2015-07-27 17:29 ` Eli Zaretskii
2015-07-28 1:09 ` Paul Eggert
2015-07-28 10:37 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B6481D.4080208@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=21020@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=wgg2@member.fsf.org \
/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.savannah.gnu.org/cgit/emacs.git
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).