public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nscd/390] New: Build fails with linux 2.4 headers using recent CVS
@ 2004-09-17 22:37 curtm4n at gmail dot com
2004-09-17 23:00 ` [Bug nscd/390] " lv at gentoo dot org
2004-09-19 21:15 ` curtm4n at gmail dot com
0 siblings, 2 replies; 3+ messages in thread
From: curtm4n at gmail dot com @ 2004-09-17 22:37 UTC (permalink / raw)
To: glibc-bugs
It seems that some recent commits cause the glibc build to fail when Linux 2.4
kernel headers are installed instead of 2.6.
Some background can be found here:
http://bugs.gentoo.org/show_bug.cgi?id=64371
With the actual error being:
../sysdeps/unix/sysv/linux/nscd_setup_thread.c: In function `setup_thread':
../sysdeps/unix/sysv/linux/nscd_setup_thread.c:40: error: `__NR_set_tid_address'
undeclared (first use in this function)
../sysdeps/unix/sysv/linux/nscd_setup_thread.c:40: error: (Each undeclared
identifier is reported only once
../sysdeps/unix/sysv/linux/nscd_setup_thread.c:40: error: for each function it
appears in.)
Perhaps __NR_set_tid_address should be defined there, like it is in
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/init.c?rev=1.48&content-type=text/x-cvsweb-markup&cvsroot=glibc
or maybe the Linux 2.4 maintainer can be persuaded to backport something from 2.6?
--
Summary: Build fails with linux 2.4 headers using recent CVS
Product: glibc
Version: 2.3.3
Status: NEW
Severity: critical
Priority: P2
Component: nscd
AssignedTo: drepper at redhat dot com
ReportedBy: curtm4n at gmail dot com
CC: curtm4n at gmail dot com,glibc-bugs at sources dot
redhat dot com
GCC host triplet: i686-pc-linux-gnu
http://sources.redhat.com/bugzilla/show_bug.cgi?id=390
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug nscd/390] Build fails with linux 2.4 headers using recent CVS
2004-09-17 22:37 [Bug nscd/390] New: Build fails with linux 2.4 headers using recent CVS curtm4n at gmail dot com
@ 2004-09-17 23:00 ` lv at gentoo dot org
2004-09-19 21:15 ` curtm4n at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: lv at gentoo dot org @ 2004-09-17 23:00 UTC (permalink / raw)
To: glibc-bugs
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |lv at gentoo dot org
http://sources.redhat.com/bugzilla/show_bug.cgi?id=390
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug nscd/390] Build fails with linux 2.4 headers using recent CVS
2004-09-17 22:37 [Bug nscd/390] New: Build fails with linux 2.4 headers using recent CVS curtm4n at gmail dot com
2004-09-17 23:00 ` [Bug nscd/390] " lv at gentoo dot org
@ 2004-09-19 21:15 ` curtm4n at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: curtm4n at gmail dot com @ 2004-09-19 21:15 UTC (permalink / raw)
To: glibc-bugs
------- Additional Comments From curtm4n at gmail dot com 2004-09-19 21:15 -------
Apparently this is fixed in CVS now.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://sources.redhat.com/bugzilla/show_bug.cgi?id=390
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-09-19 21:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-17 22:37 [Bug nscd/390] New: Build fails with linux 2.4 headers using recent CVS curtm4n at gmail dot com
2004-09-17 23:00 ` [Bug nscd/390] " lv at gentoo dot org
2004-09-19 21:15 ` curtm4n at gmail dot com
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).