From: Bruno Haible <bruno@clisp.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: bug-gnulib@gnu.org, Christian Biesinger <cbiesinger@gmail.com>
Subject: Re: time_r module does not work on MingW
Date: Tue, 12 Nov 2019 03:28:42 +0100 [thread overview]
Message-ID: <1576792.iqhKLmYyPN@omega> (raw)
In-Reply-To: <CACpOFMsymeu8Stm3J2518gU_uMTKN+mR-90W+TnrZFJ5J3R+nA@mail.gmail.com>
> Here is the testcase:
> #include "build-gnulib-gdbserver/config.h"
> #include "pathmax.h"
> #include "time.h"
>
> x86_64-w64-mingw32-g++ test.cc -I build-gnulib-gdbserver/import/ -I
> ~/binutils-gdb/gnulib/import/
>
> It turns out that the pathmax.h include is required for this to fail.
> Alternatively, including just unistd.h before time.h will fail. Error:
> https://pastebin.com/Vp8LUqaQ
>
> The enabled gnulib modules are:
> IMPORTED_GNULIB_MODULES="\ ...
Thanks. I reproduce it. Will investigate.
Bruno
next prev parent reply other threads:[~2019-11-12 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:56 time_r module does not work on MingW Christian Biesinger
2019-11-11 19:53 ` Paul Eggert
2019-11-11 19:59 ` Bruno Haible
2019-11-11 20:47 ` Christian Biesinger
2019-11-12 2:28 ` Bruno Haible [this message]
2019-11-16 12:15 ` Bruno Haible
2019-11-16 22:41 ` wctype.h compile error on mingw with GNULIB_NAMESPACE Christian Biesinger
2019-11-17 3:05 ` Bruno Haible
2019-11-17 4:40 ` Christian Biesinger
2019-11-24 19:15 ` Bruno Haible
2019-11-25 23:28 ` Christian Biesinger
2019-11-25 23:53 ` Bruno Haible
2019-11-24 14:06 ` time_r module does not work on MingW Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1576792.iqhKLmYyPN@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=cbiesinger@gmail.com \
--cc=cbiesinger@google.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).