From: Mike Crowe <mac@mcrowe.com>
To: libc-alpha@sourceware.org
Subject: Re: hppa build broken
Date: Wed, 17 Jul 2019 09:44:47 +0100 [thread overview]
Message-ID: <20190717084447.v5ovxumdq7hbhl5e@mcrowe.com> (raw)
In-Reply-To: <87d0i9g14f.fsf@oldenburg2.str.redhat.com>
On Tuesday 16 July 2019 at 22:45:04 +0200, Florian Weimer wrote:
> In file included from tst-mutex5.c:27:
> tst-mutex5.c: In function ‘do_test_clock’:
> tst-mutex5.c:76:19: error: implicit declaration of function ‘pthread_mutex_clocklock’; did you mean ‘pthread_mutex_unlock’? [-Werror=implicit-function-declaration]
> 76 | TEST_COMPARE (pthread_mutex_clocklock (&m, clockid, &ts_timeout),
> | ^~~~~~~~~~~~~~~~~~~~~~~
> ../support/check.h:103:28: note: in definition of macro ‘TEST_COMPARE’
> 103 | typedef __typeof__ (+ (left)) __left_type; \
> | ^~~~
>
> I think this is because the hppa copy of pthread.h wasn't updated for
> the recent nptl changes.
Proposed fix at https://sourceware.org/ml/libc-alpha/2019-07/msg00354.html
Mike.
next prev parent reply other threads:[~2019-07-17 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 20:45 hppa build broken Florian Weimer
2019-07-17 8:44 ` Mike Crowe [this message]
2019-07-17 16:58 ` Adhemerval Zanella
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190717084447.v5ovxumdq7hbhl5e@mcrowe.com \
--to=mac@mcrowe.com \
--cc=libc-alpha@sourceware.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).