From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: Re: test-rwlock1 failing on latest Fedora Rawhide
Date: Wed, 23 Jan 2019 21:01:19 +0100 [thread overview]
Message-ID: <1903559.vGX8tUDGlp@omega> (raw)
In-Reply-To: <20190123193730.GA9768@redhat.com>
Hi Rich,
> I cannot reproduce this locally, hence my bug report is rather devoid
> of details. However, it's 100% reproducible in Koji (the Fedora
> Rawhide build system) on *all* architectures except armv7:
>
> FAIL: test-rwlock1
> ==================
> Unexpected outcome 3
> FAIL: test-thread_create
As written in [1]:
"Unexpected outcome 3" means that the test program could not create a second
thread (other than the main thread).
On glibc systems, this typically means that the 'test-rwlock1' program has not
been linked with '-lpthread'.
> The full log is here:
>
> https://kojipkgs.fedoraproject.org//work/tasks/4382/32214382/build.log
The configure command-line looks right.
I see
LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
A global "-Wl,--as-needed" has the effect of removing libraries like
-lpthread from the link. Which would explain the symptom.
What do the other elements of LDFLAGS do?
Bruno
[1] http://lists.gnu.org/archive/html/coreutils/2018-02/msg00020.html
next prev parent reply other threads:[~2019-01-23 20:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 19:37 test-rwlock1 failing on latest Fedora Rawhide Richard W.M. Jones
2019-01-23 20:01 ` Bruno Haible [this message]
2019-01-23 20:45 ` Richard W.M. Jones
2019-01-23 21:03 ` Dmitry V. Levin
2019-01-23 21:14 ` Richard W.M. Jones
2019-01-23 22:09 ` Dmitry V. Levin
2019-01-23 22:24 ` Richard W.M. Jones
2019-01-23 22:38 ` Dmitry V. Levin
2019-01-24 3:18 ` Bruno Haible
2019-01-24 3:31 ` Bruno Haible
2019-01-24 3:49 ` Bruno Haible
2019-01-24 8:57 ` Richard W.M. Jones
2019-01-24 8:50 ` Richard W.M. Jones
2019-01-23 21:17 ` Michael Hudson-Doyle
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=1903559.vGX8tUDGlp@omega \
--to=bruno@clisp.org \
--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).