From: Kumar Gala <galak@kernel.crashing.org>
To: Bruce_Leonard@selinc.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Question about "native" compiling
Date: Fri, 23 May 2008 01:39:22 -0500 [thread overview]
Message-ID: <4B12DBAE-BB24-4114-BFEB-FF369E461622@kernel.crashing.org> (raw)
In-Reply-To: <OF2C9C3CB1.4A6FAC88-ON88257451.00760B81-88257451.00761D72@selinc.com>
On May 22, 2008, at 4:30 PM, Bruce_Leonard@selinc.com wrote:
> Hi all,
>
> 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?
>
> Thanks for any advice or pointers to other places where I can find
> information.
Do you plan on running the same Ubuntu install (for ppc32) on the
8347e? If not you'll need to be careful to ensure libraries, etc are
the same or compatible.
- k
next prev parent reply other threads:[~2008-05-23 6:39 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
2008-05-23 6:39 ` Kumar Gala [this message]
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=4B12DBAE-BB24-4114-BFEB-FF369E461622@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--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