public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gmsoft at tuxicoman dot be" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/5923] New: glibc HEAD compile failure on hppa with --enable-kernel=2.6.22 or higher
Date: Wed, 12 Mar 2008 22:29:00 -0000 [thread overview]
Message-ID: <20080312222825.5923.gmsoft@tuxicoman.be> (raw)
When using --enable-kernel=2.6.22 or higher, __ASSUME_PRIVATE_FUTEX becomes
defined (see sysdeps/unix/sysv/linux/kernel-features.h) then the following
invalid macro definition is used in
ports/sysdeps/unix/sysv/linux/hppa/nptl/lowlevellock.h:114 :
# define lll_private_futex_timed_wait(futex, val, timeout)
Attached patch solves the problem
--
Summary: glibc HEAD compile failure on hppa with --enable-
kernel=2.6.22 or higher
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: gmsoft at tuxicoman dot be
CC: carlos at systemhalted dot org,glibc-bugs at sources dot
redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5923
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2008-03-12 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 22:29 gmsoft at tuxicoman dot be [this message]
2008-03-12 22:29 ` [Bug nptl/5923] " gmsoft at tuxicoman dot be
2008-03-12 22:48 ` [Bug ports/5923] " drepper at redhat dot com
2008-03-13 17:57 ` carlos at codesourcery dot com
2008-03-14 23:42 ` cvs-commit at gcc dot gnu dot org
2008-03-15 14:49 ` carlos at codesourcery dot com
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=20080312222825.5923.gmsoft@tuxicoman.be \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).