From: Andreas Jaeger <aj@suse.de>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: current glibc does not build
Date: Sat, 08 Jul 2006 09:57:00 -0000 [thread overview]
Message-ID: <m33bdcxvub.fsf@gromit.moeb> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
building glibc fails for me with:
pthread_mutex_init.c: In function ‘__pthread_mutex_init’:
pthread_mutex_init.c:84: error: ‘PTHREAD_MUTEX_PRIO_INHERIT_NP’ undeclared (first use in this function)
pthread_mutex_init.c:84: error: (Each undeclared identifier is reported only once
pthread_mutex_init.c:84: error: for each function it appears in.)
pthread_mutex_init.c:88: error: ‘PTHREAD_MUTEX_PRIO_PROTECT_NP’ undeclared (first use in this function)
The constant is not defined anywhere in current glib cvs,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
reply other threads:[~2006-07-08 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33bdcxvub.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.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).