bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: "Tim Rühsen" <tim.ruehsen@gmx.de>
Subject: Re: Tests on MinGW: undef ref pthread_mutex_lock/unlock
Date: Thu, 11 Apr 2019 09:58:47 +0200	[thread overview]
Message-ID: <11626304.0g4GYiqlB1@omega> (raw)
In-Reply-To: <4256bd91-1053-6168-d2c4-f42549a2b488@gmx.de>

Hi Tim,

> Running gnulib tests on MinGW (current Debian unstable) fail:
> 
> /usr/bin/x86_64-w64-mingw32-ld:
> libtests.a(localename.o):localename.c:(.text+0x10): undefined reference
> to `pthread_mutex_lock'
> /usr/bin/x86_64-w64-mingw32-ld:
> libtests.a(localename.o):localename.c:(.text+0x83): undefined reference
> to `pthread_mutex_unlock'
> /usr/bin/x86_64-w64-mingw32-ld:
> libtests.a(localename.o):localename.c:(.text+0xa8): undefined reference
> to `pthread_mutex_unlock'
> collect2: error: ld returned 1 exit status

For analyzing this, we would need the generated
  - config.log,
  - config.status,
  - config.h.

Bruno



  reply	other threads:[~2019-04-11  7:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  7:18 Tests on MinGW: undef ref pthread_mutex_lock/unlock Tim Rühsen
2019-04-11  7:58 ` Bruno Haible [this message]
2019-04-11  8:49   ` Tim Rühsen
2019-04-11 18:56     ` Bruno Haible
2019-04-11 19:35       ` Tim Rühsen
2019-04-11 20:33       ` Tim Rühsen
2019-04-12  0:26         ` Bruno Haible
2019-04-12  1:26           ` Eric Blake
2019-04-12  7:15           ` Tim Rühsen
2019-04-13 15:07             ` 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=11626304.0g4GYiqlB1@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=tim.ruehsen@gmx.de \
    /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).