From: Michael Meissner <meissner@tiktok.cygnus.com>
To: Gerd Knorr <kraxel@goldbach.in-berlin.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MVME 2306 almost up and running
Date: Thu, 4 Mar 1999 18:22:03 -0500 [thread overview]
Message-ID: <19990304182203.A1856@tiktok.cygnus.com> (raw)
In-Reply-To: <199903041951.UAA00814@macintoy.masq.in-berlin.de>; from Gerd Knorr on Thu, Mar 04, 1999 at 08:51:55PM +0100
On Thu, Mar 04, 1999 at 08:51:55PM +0100, Gerd Knorr wrote:
>
> > Hi,
> >
> > My final question : our board now finally boots, it can mount an
> > NFS partition as root fs, but does anybody know where on the Internet
> > I can find a file system tree with the binaries for LinuxPPC ? I mean,
> > like Slackware, but for LinuxPPC. (We have no other [spare] PPC based
> > machines, so I need a full binary file tree to set up on the NFS fs).
>
> Just download the basic rpm's and install them on the NFS Server
> with "rpm --root=/export/nfsroot4ppc -i *.rpm".
I think the point is that the normal rpm's (ie, ftp.linuxppc.{org,com}) won't
work too well on an ppc860, since that machine does not have a FPU, and the
kernel support for emulating fp might not be present or even if present, too
slow.
One thought is to build a cross compiler on some other system, and manually
build the compiler and enough tools to run native and then bootstrap the old
fashioned way (you probably want to use the --with-cpu=860 switch when
configuring, so that binaries by default don't reference the fpu). However,
setting up a cross compiler is somewhat tricky if you've never done it before.
--
Michael Meissner, Cygnus Solutions
PO Box 98, Ayer Massachusetts, USA 01432-0098
meissner@cygnus.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-04 23:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <David De Ridder's message of "Thu, 4 Mar 1999 17:35:53 +0100 (MET)">
1999-03-04 16:35 ` MVME 2306 almost up and running David De Ridder
1999-03-04 19:51 ` Gerd Knorr
1999-03-04 23:22 ` Michael Meissner [this message]
1999-03-05 10:21 ` Gabriel Paubert
1999-03-05 15:59 ` Michael Meissner
1999-03-05 10:45 ` David De Ridder
1999-03-05 10:46 ` David De Ridder
1999-03-05 11:49 ` Gabriel Paubert
1999-03-05 13:47 ` David De Ridder
[not found] ` <3.0.6.32.19990307142206.0081d960@hsins.uia.ac.be>
1999-03-07 20:41 ` Michael Lundkvist
1999-03-12 13:10 ` Gabriel Paubert
1999-03-19 15:46 ` Matt Porter
1999-03-21 14:52 ` Michael Lundkvist
1999-03-21 15:05 ` Michael Lundkvist
1999-03-22 10:40 ` David De Ridder
1999-03-22 11:06 ` Michael Lundkvist
1999-03-22 12:01 ` David De Ridder
1999-03-22 12:28 ` Michael Lundkvist
1999-03-22 12:45 ` David De Ridder
1999-03-22 13:24 ` Michael Lundkvist
1999-03-22 16:46 ` David De Ridder
1999-03-23 9:51 ` Michael Lundkvist
1999-04-02 11:22 ` MVME2306 problems dragging on David De Ridder
1999-04-02 14:12 ` VALETTE Eric
1999-04-02 15:22 ` David De Ridder
1999-04-02 15:28 ` VALETTE Eric
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=19990304182203.A1856@tiktok.cygnus.com \
--to=meissner@tiktok.cygnus.com \
--cc=kraxel@goldbach.in-berlin.de \
--cc=linuxppc-dev@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).