From: Maxim Osipov <maxim.osipov@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Daniel Jacobowitz <dan@debian.org>, linux-mips@linux-mips.org
Subject: Re: glibc-2.3.4 mips64 compilation failure
Date: Fri, 27 May 2005 14:15:13 +0400 [thread overview]
Message-ID: <6097c4905052703152b50f717@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0505261815330.29423@blysk.ds.pg.gda.pl>
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,
Maxim
On 5/26/05, Maciej W. Rozycki <macro@linux-mips.org> 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 ftp://ftp.linux-mips.org/pub/linux/mips/crossdev/i386-linux/mips64-linux.
> > > Compilation fails with following messages:
> >
> > Looks like your kernel headers are too old.
>
> Or too new, sigh... See:
> "http://sources.redhat.com/bugzilla/show_bug.cgi?id=758". 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
>
>
next prev parent reply other threads:[~2005-05-27 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 16:32 glibc-2.3.4 mips64 compilation failure Maxim Osipov
2005-05-26 17:06 ` Daniel Jacobowitz
2005-05-26 17:26 ` Maciej W. Rozycki
2005-05-26 19:05 ` Daniel Jacobowitz
2005-05-26 19:34 ` Maciej W. Rozycki
2005-05-26 20:08 ` Daniel Jacobowitz
2005-05-26 20:15 ` Daniel Jacobowitz
2005-05-26 20:22 ` Maciej W. Rozycki
2005-05-26 20:24 ` Daniel Jacobowitz
2005-05-26 20:33 ` Maciej W. Rozycki
2005-05-27 10:15 ` Maxim Osipov [this message]
2005-05-31 14:28 ` Maciej W. Rozycki
[not found] <429C8F71.6080606@siemens.com>
2005-05-31 16:30 ` Maxim Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6097c4905052703152b50f717@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=maxim@mox.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.