From: Brendan Simon <bsimon@ctam.com.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: glibc for mpc860
Date: Fri, 10 Sep 1999 10:41:58 +1000 [thread overview]
Message-ID: <37D853D5.54331958@ctam.com.au> (raw)
Dan Malek wrote:
> > Any chance you could put your libc-1.99 (or a pointer to it) up at
> > ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded/ ?
> It's been there a long time....libc-1.99-8xx.somthing_or_other.
> It's compiled with the -mcpu=860 flag, has the cache line stuff
> patched (so you can run copyback on the 8xx), and has the floating
> point assembler instructions removed. It was built from
> glibc-0.961212-1o, and is a tar image.
What is the latest glibc that supports the MPC860 processor and where
can I get it. I dowloaded the latest glibc (2.1.1) from a GNU mirror
and it compiled fine with my egcs-1.1.2 powerpc-linux cross-compiler. I
tried adding the -mcpu=860 option and it barfed. Problems with floating
point instructions as far as I can tell. I assume that the glibc
developers do not consider targets without a floating point processor as
a non-priority (I wish the MPC860 had an FPU). It looks like others
have ported/modified some glibc sources to work with the -mcpu=860
option. What version is it and where can I get it. Are the modified
glibc sources available as an archive and/or are there patches for any
other glibc sources.
Thanks,
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-10 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 0:41 Brendan Simon [this message]
[not found] ` <37D88E48.23A1728C@jlc.net>
1999-09-10 6:37 ` glibc for mpc860 Brendan Simon
1999-09-10 10:08 ` Marcus Sundberg
1999-09-10 11:57 ` Kenneth Johansson
1999-09-13 2:37 ` Brendan Simon
1999-09-13 4:45 ` Dan Malek
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=37D853D5.54331958@ctam.com.au \
--to=bsimon@ctam.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).