From: David Jander <david.jander@protonic.nl>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Compiling glibc-2.3.2 (debian) on mpc8xx ;-)
Date: Tue, 9 Mar 2004 09:53:54 +0100 [thread overview]
Message-ID: <200403090953.54598.david.jander@protonic.nl> (raw)
Hi all,
I proudly announce that we finally have the first two prototypes of our boards
based on the MPC852T running. Until now it looks like one of those lucky
"one-time-right" designs, since it went flawless until now. We have 64 MByte
SDRAM on-board, an ethernet Phy (FEC), 4 Mbyte Flash, etc...
Since I'm quite crazy, and love running "big-stuff" on "small-things" I
decided to install Debian-unstable (sid) on an nfs-mounted root.
So far, so good. I compiled a kernel with FPU-emulation just in case, and went
through the installation of the base system using glibc-2.3.1 from ELDK
binaries plugged on top of the version from debian, to avoid further
incompatibilities.
Now, after apt-getting a hell of a lot of fancy software (all running quite
fine until now - except floating-point-libc stuff), the time has come to
recompile GlibC..... on the target!
Question: What do I have to patch exactly before compiling? I want to leave
floating-point stuff in there for now to stay compatible with
debian-binaries. AFAIK there is (was?) an issue with
sysdeps/powerpc/powerpc32/memset.S and sysdeps/powerpc/powerpc32/dl-machine.c
containing code that assumed a cache-line of different size than that of the
MPC8xx. Is this still the case in glibc-2.3.2? Hasn't this been patched in
the official sources?
What else do I have to look out for? What other patches to apply? Where to get
them from?
Greetings,
--
David Jander
Protonic Holland.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-03-09 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 8:53 David Jander [this message]
2004-03-09 9:45 ` Compiling glibc-2.3.2 (debian) on mpc8xx ;-) Wolfgang Denk
[not found] <200403091240.40660.david.jander@protonic.nl>
2004-03-09 12:09 ` Wolfgang Denk
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=200403090953.54598.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--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).