This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
Trying to build a MIPS64 glibc
- From: Jonathan Day <imipak at yahoo dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 12 Sep 2005 00:52:52 -0700 (PDT)
- Subject: Trying to build a MIPS64 glibc
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Vm4Se4CI9S/i9nVDO6ps/PQ07VhEN3x7SI2j6laRntAN7JHs+l9RY9TAMN+cPsJOIxkRlbNvpUfFk0qXUEb4/95dHNJRYkV8miRvO2fopvQOPVro83s1djjTydLxVQgwCRALptsUqJrJ5EAejCaMVRUNMBMni+4ClDmjXk+QT40= ;
Hi,
I worked through the first part of a sequence of
problems on the GCC mailing list. Well, now I've got
problems with Glibc. In the case of glibc, I've tested
using a vanilla glibc 2.3.5, a 2.3.5 patched according
to the "Linux From Scratch" website, and the version
in CVS (on the 9th).
Everything builds fine, until it gets into the posix
directory. The error message I'm getting is as
follows:
../sysdeps/unix/sysv/linux/mips/pread.c: In function
'__libc_pread':
../sysdeps/unix/sysv/linux/mips/pread.c:66: error:
'__NR_N64_pread' undeclared (first use in this
function)
../sysdeps/unix/sysv/linux/mips/pread.c:66: error:
(Each undeclared identifier is reported only once
../sysdeps/unix/sysv/linux/mips/pread.c:66: error: for
each function it appears in.)
make[2]: *** [/usr/src/mips/obj/glibc/posix/pread.o]
Error 1
make[2]: Leaving directory
`/usr/src/mips/src/glibc-2.3.5/posix'
make[1]: *** [posix/subdir_lib] Error 2
make[1]: Leaving directory
`/usr/src/mips/src/glibc-2.3.5'
make: *** [all] Error 2
The specific line involved is:
result = INLINE_SYSCALL (pread, 4, fd, CHECK_N (buf,
count), count, offset);
Grepping the source tree, include files and anything
else I could think of did not reveal to me where
__NR_N64_pread is defined (or, in this case, should be
defined!) Either in glibc, gcc, binutils or the kernel
header files.
I am stumped, to be honest. Without knowing where the
error is coming from, it's hard to dummy something up
-or- produce much in the way of a meaningful bug
report.
Has anyone successfully compiled glibc for a
MIPS64-unknown-Linux-Gnu target?
Has anyone any clues as to what might be generating
this error message I'm getting?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com