[Top] [All Lists]

Re: glibc-2.3.4 mips64 compilation failure

To: "Maciej W. Rozycki" <>
Subject: Re: glibc-2.3.4 mips64 compilation failure
From: Maxim Osipov <>
Date: Fri, 27 May 2005 14:15:13 +0400
Cc: Daniel Jacobowitz <>,
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jy4nJr/yDJe+E1jiVaWCSxITziao/z6CWBsVGqakyU7dnxrn/iugAc65+hxikHEhwCTYTT0Ibmy5AK/2KSY3HAw/s7pci/SzoFO0aF2mbu4pY343IuA9T1JFeyNfQUnd5+KNRRN2ssqynWFR5sL9xXfZNXPJ5ju3B/bKfBF/z2Y=
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <>
Hmm... I don't know. Both 2.4.26 and 2.6.10 headers do not contain
this call number in unistd.h for N64, but glibc tries to generate a
stub referencing to undefined __NR_sendfile64, and I got this
assembler error.

I tried various kernel/glibc configurations and result is the same -
we fail on sendfile64 or time.

Do anyone have a clue what is happening? AFAIK, some people already
had success building glibc for mips64. Probably I miss something?

Best regards,

On 5/26/05, Maciej W. Rozycki <> wrote:
> On Thu, 26 May 2005, Daniel Jacobowitz wrote:
> > > I am trying to build glibc-2.3.4 using binutils-2.15 and gcc-3.4.3
> > > from 
> > >
> > > Compilation fails with following messages:
> >
> > Looks like your kernel headers are too old.
>  Or too new, sigh...  See:
> "";.  Unfortunately
> it's not clear to me what "the 2.3 branch inclusion criteria" are and it's
> a pity the MIPS port of glibc is unmaintained these days...
>   Maciej

<Prev in Thread] Current Thread [Next in Thread>