bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Christian Biesinger <cbiesinger@gmail.com>
Subject: Re: time_r module does not work on MingW
Date: Mon, 11 Nov 2019 20:59:55 +0100	[thread overview]
Message-ID: <12491381.p8F8e0VtCo@omega> (raw)
In-Reply-To: <CACpOFMuPeLfjP+e6kEyV+Z4n_q9P+4q0UEG5EMfHXWx=nXn+4Q@mail.gmail.com>

Hi,

Christian Biesinger wrote:
> 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

It is hard for me to do guesswork, based on a large set of sources such
as gdb and a log file that shows mixed output from two parallel processes
(the revenge of "make -j2").

Can you please provide a simple test case?

Or at least help the investigation by showing the values of
  GNULIB_TIME_R
  REPLACE_LOCALTIME_R
  HAVE_DECL_LOCALTIME_R
that you find in config.status? Also we would need to know whether
the gdb build defines GNULIB_NAMESPACE and whether the source file
(amd64.c) starts with '#include <config.h>'.

Bruno



  parent reply	other threads:[~2019-11-11 20:00 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 [this message]
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=12491381.p8F8e0VtCo@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=cbiesinger@gmail.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).