From: Dan Malek <dmalek@jlc.net>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: GLIBC wont compile for MPC860
Date: Mon, 06 Sep 1999 01:57:52 -0400 [thread overview]
Message-ID: <37D357E0.7E648C4A@jlc.net> (raw)
In-Reply-To: 19990906011506.87848730@elph.research.canon.com.au
Graham Stoney wrote:
> I think newlib would be a promising candidate given its emphasis on small size,
Yeah, I suppose we should look at it. It is nice to use something
already ported and compiled for the PPC, though. Keeping it all
in the family makes it much easier as lots of other people are
using it.
> My application also needs threads, but I'm hoping I might be able to drop
I just use clone() straight away and I like the implementation
of Linux threads.
> ...I'll just drop lots of RAM in and link statically against glibc-2.1.2.
You may not need lots of RAM for a static linked application. The
linker only pulls what it needs form the library. I have done
several applications where static linking required both less
file system storage and real memory space.
> Sure, but I'm cross compiling from an Intel box and it would be nice to be able
If you ever used a Linux/PPC development host (IBM, Motorola, Apple)
you would never use an Intel box for this stuff. It is so much
faster and easier with a PPC host.
> 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.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-09-06 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 1:12 GLIBC wont compile for MPC860 Brendan Simon
1999-08-30 18:26 ` Scott Wood
1999-08-31 0:39 ` Graham Stoney
1999-09-01 20:27 ` Scott Wood
1999-09-01 21:47 ` David Edelsohn
1999-09-02 12:27 ` Marcus Sundberg
1999-09-03 2:15 ` Graham Stoney
1999-09-03 2:40 ` Michael Meissner
1999-09-03 12:18 ` Marcus Sundberg
1999-09-03 15:48 ` Dan Malek
1999-09-03 15:53 ` Grant Erickson
1999-09-06 1:15 ` Graham Stoney
1999-09-06 5:57 ` Dan Malek [this message]
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=37D357E0.7E648C4A@jlc.net \
--to=dmalek@jlc.net \
--cc=greyham@research.canon.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).