* Question about "native" compiling
@ 2008-05-22 21:30 Bruce_Leonard
2008-05-22 21:55 ` Scott Wood
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Bruce_Leonard @ 2008-05-22 21:30 UTC (permalink / raw)
To: linuxppc-embedded
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.
Bruce
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Question about "native" compiling
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
2 siblings, 0 replies; 5+ messages in thread
From: Scott Wood @ 2008-05-22 21:55 UTC (permalink / raw)
To: Bruce_Leonard; +Cc: linuxppc-embedded
Bruce_Leonard@selinc•com wrote:
> 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?
You can run 32-bit userspace on a G5 -- it's probably even the default
in most distributions.
-Scott
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Question about "native" compiling
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
2 siblings, 0 replies; 5+ messages in thread
From: Rune Torgersen @ 2008-05-22 22:25 UTC (permalink / raw)
To: Bruce_Leonard, linuxppc-embedded
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Question about "native" compiling
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
2008-05-23 17:22 ` Bruce_Leonard
2 siblings, 1 reply; 5+ messages in thread
From: Kumar Gala @ 2008-05-23 6:39 UTC (permalink / raw)
To: Bruce_Leonard; +Cc: linuxppc-embedded
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-05-23 17:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2008-05-23 17:22 ` Bruce_Leonard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox