From: David Jander <david.jander@protonic.nl>
To: Adrian Reber <adrian@lisas.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Best hardware platform for native compiling...
Date: Tue, 21 Jul 2009 12:31:36 +0200 [thread overview]
Message-ID: <200907211231.37299.david.jander@protonic.nl> (raw)
In-Reply-To: <20090721095251.GG32034@lisas.de>
On Tuesday 21 July 2009 11:52:51 you wrote:
> On Tue, Jul 21, 2009 at 11:16:52AM +0200, David Jander wrote:
> > For bigger systems we often run a debian-derived OS like Ubuntu, and many
> > pieces are compiled natively on the target... just because it is easy and
> > quick to do, and cross-compiling certain packages can be a real pain.
> > But, a 400 MHz e300 core is not really fast for compiling, so I have been
> > considering buying some sort of PowerPC-based system with a faster
> > processor, just as a "build-server" (a G5 would do wonders I guess).
> >
> > It seems like the only real option is one of the smaller IBM Power
> > servers, but that seems overkill to me. We also don't feel like buying
> > some old second-hand Apple gear.
> >
> > Is there any other available and affordable platform that can be used to
> > run linux and compile software natively for 32-bit PowerPC?
>
> Have a look at the YDL PowerStation:
>
> http://us.fixstars.com/products/powerstation/
>
> It is more or less a quad G5.
This looks great! Thanks a lot for the tip.
I still have to figure out how to get one of these delivered to Europe, but
that shouldn't be such a big deal...
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2009-07-21 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 9:16 Best hardware platform for native compiling David Jander
[not found] ` <20090721095251.GG32034@lisas.de>
2009-07-21 10:31 ` David Jander [this message]
2009-07-21 12:00 ` Gabriel Paubert
2009-07-21 12:47 ` Benjamin Herrenschmidt
2009-07-22 20:18 ` Olof Johansson
2009-07-21 13:07 ` David Jander
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=200907211231.37299.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=adrian@lisas.de \
--cc=linuxppc-dev@ozlabs.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).