bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@gmail.com>
To: bug-gnulib@gnu.org
Subject: time_r module does not work on MingW
Date: Mon, 11 Nov 2019 10:56:08 -0800	[thread overview]
Message-ID: <CACpOFMuPeLfjP+e6kEyV+Z4n_q9P+4q0UEG5EMfHXWx=nXn+4Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

Hello!

I tried to use the time_r module with GDB (using Gnulib
revision 38237baf99386101934cd93278023aa4ae523ec0)

However, I found that it does not compile, see logs at:
https://gdb-buildbot.osci.io/#/builders/23/builds/934

Apparently, the MingW time.h has localtime_r and gmtime_r defined as
__forceinline functions outside of the extern "C" block, so they use C++
linkage, whereas gnulib expects C linkage.

I'm not sure what the best fix is but this seems unfortunate?

Christian

[-- Attachment #2: Type: text/html, Size: 725 bytes --]

             reply	other threads:[~2019-11-11 19:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 18:56 Christian Biesinger [this message]
2019-11-11 19:53 ` time_r module does not work on MingW Paul Eggert
2019-11-11 19:59 ` Bruno Haible
2019-11-11 20:47   ` Christian Biesinger
2019-11-12  2:28     ` Bruno Haible
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='CACpOFMuPeLfjP+e6kEyV+Z4n_q9P+4q0UEG5EMfHXWx=nXn+4Q@mail.gmail.com' \
    --to=cbiesinger@gmail.com \
    --cc=bug-gnulib@gnu.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.
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).