This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Compile-time error


On 6 Mar 2007, Michael Muratet told this:
> I thought I had followed the install docs completely, but I am getting
> the following error when I compile on a Dell PowerEdge running RedHat
> 7.2

A *lot* of things are going to need upgrading before you can build
recent versions of glibc on that. GCC, binutils, even texinfo.

> ../nptl/sysdeps/unix/sysv/linux/raise.c: In function 'raise':
> ../nptl/sysdeps/unix/sysv/linux/raise.c:42: error: '__NR_gettid'
> undeclared (first use in this function)
> ../nptl/sysdeps/unix/sysv/linux/raise.c:42: error: (Each undeclared
> identifier is reported only once
> ../nptl/sysdeps/unix/sysv/linux/raise.c:42: error: for each function it
> appears in.)
> ../nptl/sysdeps/unix/sysv/linux/raise.c:71: error: '__NR_tkill'
> undeclared (first use in this function)
> make[2]: *** [/usr/local/glibc-build/signal/raise.o] Error 1
> make[2]: Leaving directory `/usr/local/glibc-2.4/signal'
> make[1]: *** [signal/subdir_lib] Error 2
> make[1]: Leaving directory `/usr/local/glibc-2.4'
>
> A search of the web didn't turn up much, except maybe there's a missing
> header file associated with a more recent kernel. The kernel here is
> 2.4.7.10smp. Can anyone point me in the right direction?

Unless you turn off all threading support (and maybe not even then),
glibc 2.5 won't compile without kernel 2.6 header files, and there's no
way you'll get threading to work without running a 2.6.x kernel
(although RH did backport a lot of the necessary bits to some late 2.4.x
kernels for RH8, I think: the memory fades, it was so long ago). Stick
with an older glibc (2.3.x or older) which provides the (much less
POSIX-conforming and more inefficient) LinuxThreads threading
implementation, or upgrade your kernel.

(How are you keeping something that old up to date re security, anyway? 
Compiling everything needed by hand? Sure, you can *do* that, but it's
a bit laborious.)

-- 
`In the future, company names will be a 32-character hex string.'
  --- Bruce Schneier on the shortage of company names


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]