LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rune Torgersen" <runet@innovsys.com>
To: <Bruce_Leonard@selinc.com>, <linuxppc-embedded@ozlabs.org>
Subject: RE: Question about "native" compiling
Date: Thu, 22 May 2008 17:25:28 -0500	[thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B046E8024@ismail.innsys.innovsys.com> (raw)
In-Reply-To: <OF2C9C3CB1.4A6FAC88-ON88257451.00760B81-88257451.00761D72@selinc.com>

linuxppc-embedded-bounces+runet=3Dinnovsys.com@ozlabs.org wrote:
> Hi all,
>=20
> I apologize if the list finds this off topic, but I'm at a
> loss of who to
> ask the question and thought this would be a good place to
> start.  Our
> target is an MPC8347E PowerQUICC II Pro, and we're using the
> latest kernel
> (2.6.25).  We started this project by building on x86 and doing
> cross-compiling to the powerpc target.  As the project
> progressed and we
> started adding applications we found that we couldn't cross-compile
> postgress among other things.  So we switched to native
> compilation on the
> target.  Problem is, it's extreamly slow.  Now our idea is to get our
> hands on a PowerPC based Mac, load it up with Ubuntu and do
> native builds
> on that.  The question is, which Mac to get?  The concern is
> this: a G5 is
> 64-bit but the 8347E is 32-bit.  If we do our compiles on a G5 is it
> really a 'native' compile or is it a cross-compile and we're
> back in the
> same boat as we were with the x86?  Should we use a G4 instead?
>=20
> Thanks for any advice or pointers to other places where I can find
> information.=20

We use a dual G5 to do the exact same thing.
We have a compiler buildt on our target board (Freescale 8280), and on
the G5 we make sure that this compiler is being used (by chrooting into
a copy of the filesystem used on the target).=20
Then we compile all our apps .=20
Only thing we have to do speciial, is to add
--build=3Dpowerpc-unknown-linux-gnu --host=3Dpowerpc-unknown-linux-gnu =
to
the ./configure cammand line.

  parent reply	other threads:[~2008-05-22 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 21:30 Question about "native" compiling Bruce_Leonard
2008-05-22 21:55 ` Scott Wood
2008-05-22 22:25 ` Rune Torgersen [this message]
2008-05-23  6:39 ` Kumar Gala
2008-05-23 17:22   ` Bruce_Leonard

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=DCEAAC0833DD314AB0B58112AD99B93B046E8024@ismail.innsys.innovsys.com \
    --to=runet@innovsys.com \
    --cc=Bruce_Leonard@selinc.com \
    --cc=linuxppc-embedded@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