This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/3956] New: nptl in glibc-2.5 fails to compile on ppc with kernel 2.4.17
- From: "mike at tedder dot cc" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 2 Feb 2007 09:56:48 -0000
- Subject: [Bug nptl/3956] New: nptl in glibc-2.5 fails to compile on ppc with kernel 2.4.17
- Reply-to: sourceware-bugzilla at sourceware dot org
I am unable to compile nptl within glibc-2.5 due to the '__NR_tkill' symbol
being undefined. The compile error occurs in raise.c:
gcc ../nptl/sysdeps/unix/sysv/linux/raise.c -c -std=gnu99 -O2 -Wall -Winline -
Wwrite-strings -fmerge-all-constants -g -mnew-mnemonics -Wstrict-prototypes -
mlong-double-128 -I../include -I/mnt/home/bpoint/src/glibc-2.5-objdir/
signal -I/mnt/home/bpoint/src/glibc-2.5-objdir -I../sysdeps/powerpc/powerpc32/
elf -I../sysdeps/powerpc/elf -I../sysdeps/unix/sysv/linux/powerpc/powerpc32/fpu
-I../sysdeps/powerpc/powerpc32/fpu -I../nptl/sysdeps/unix/sysv/linux/powerpc/
powerpc32 -I../sysdeps/unix/sysv/linux/powerpc/powerpc32 -I../nptl/sysdeps/unix/
sysv/linux/powerpc -I../sysdeps/unix/sysv/linux/powerpc -I../sysdeps/ieee754/
ldbl-128ibm -I../sysdeps/ieee754/ldbl-opt -I../nptl/sysdeps/unix/sysv/linux -
I../nptl/sysdeps/pthread -I../sysdeps/pthread -I../sysdeps/unix/sysv/linux -I../
sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/
inet -I../nptl/sysdeps/unix/sysv -I../sysdeps/unix/sysv -I../sysdeps/unix/
powerpc -I../nptl/sysdeps/unix -I../sysdeps/unix -I../sysdeps/posix -I../
sysdeps/powerpc/powerpc32 -I../sysdeps/wordsize-32 -I../sysdeps/powerpc/fpu -
I../nptl/sysdeps/powerpc -I../sysdeps/powerpc -I../sysdeps/ieee754/dbl-64 -I../
sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../
sysdeps/generic -I../nptl -I.. -I../libio -I. -D_LIBC_REENTRANT -include ../
include/libc-symbols.h -o /mnt/home/bpoint/src/glibc-2.5-objdir/signal/
raise.o -MD -MP -MF /mnt/home/bpoint/src/glibc-2.5-objdir/signal/raise.o.dt -MT
/mnt/home/bpoint/src/glibc-2.5-objdir/signal/raise.o
../nptl/sysdeps/unix/sysv/linux/raise.c: In function 'raise':
../nptl/sysdeps/unix/sysv/linux/raise.c:71: error: '__NR_tkill' undeclared
(first use in this function)
../nptl/sysdeps/unix/sysv/linux/raise.c:71: error: (Each undeclared
identifier is reported only once
../nptl/sysdeps/unix/sysv/linux/raise.c:71: error: for each function it
appears in.)
make[2]: *** [/mnt/home/bpoint/src/glibc-2.5-objdir/signal/raise.o] Error 1
For the record, my /usr/include/asm-ppc/unistd.h file only contains up to
syscall 207:
#define __NR_madvise 205
#define __NR_mincore 206
#define __NR_gettid 207
#define __NR(n) #n
Searching the net reveals that newer kernel includes show __NR_tkill as being
#defined as 208, however, my kernel is built into ROM and cannot be updated. I
already checked the HEAD revision of raise.c in CVS, but it hasn't been touched
in 2 years.
In case if it's necessary, here's my uname -a:
bpoint@kuro-box.tedder.cc:~/src/glibc-2.5-objdir$ uname -a
Linux kuro-box.tedder.cc 2.4.17_kuro-box #4 2004年 4月 16日 金曜日 11:45:05 JST
ppc unknown unknown GNU/Linux
And gcc version:
bpoint@kuro-box.tedder.cc:~/src/glibc-2.5-objdir$ gcc -v
Using built-in specs.
Target: powerpc-unknown-linux-gnu
Configured with: ../gcc-4.1.1/configure --prefix=/usr --with-cpu=603 --enable-
languages=c,c++ --disable-checking --disable-altivec
Thread model: posix
gcc version 4.1.1
Any suggestions for a workaround, or should I just use Linuxthreads instead of
NPTL?
--
Summary: nptl in glibc-2.5 fails to compile on ppc with kernel
2.4.17
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: mike at tedder dot cc
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: powerpc-unknown-linux-gnu
GCC host triplet: powerpc-unknown-linux-gnu
GCC target triplet: powerpc-unknown-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=3956
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.