From: Dr. Craig Hollabaugh <hidden> Date: 2002-08-22 23:39:18
At 09:36 AM 8/22/2002 +0200, Marius Groeger wrote:
2. The "emulation" will never be 100%. Maybe 99%. Maybe 99.99%. That last
fraction can be a major PITA, because it is not obvious. To compile a
kernel you need a lot of tools with a lot of explicit and implicit twists
to them. It is just a gut feeling that I wouldn't want to rely on this,
if I don't have to. The native way just seems the better way to do it to
me.
Just because your running on Linux doesn't mean anything because your duplicating
the environment for cross-compiling anyway. So what does it matter if cygwin runs
the cross tools or if Linux runs them?
I'm curious ...
How many out there actually are compiling PPC code natively on a PowerPC Linux box for their embedded devices?
If so, do you run the same development versions on your desktop?
How do you handle the FPU issues?
Craig
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Dan Malek <hidden> Date: 2002-08-23 05:18:32
Dr. Craig Hollabaugh wrote:
I'm curious ...
How many out there actually are compiling PPC code natively on a PowerPC Linux box for their embedded devices?
Me.
If so, do you run the same development versions on your desktop?
Almost :-)
How do you handle the FPU issues?
For 4xx/8xx I'll use a cross compiler, all other PowerPCs have FPUs.
For embedded Altivecs I have to use the host compiler.
I do all of my development for all embedded processors on a PowerMac running YDL.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Magnus Damm <hidden> Date: 2002-08-23 09:15:17
How many out there actually are compiling PPC code natively
on a PowerPC Linux box for their embedded devices?
Not me. I cross compile all my distributions from x86 hosts.
I like the idea of separating the target system from the
host system. To keep track of used libraries and to be able
to recreate the same distribution in the future with another
host.
I've always wanted a sleek laptop from apple,
but I would like more than one mouse button...
/ magnus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Kenneth Johansson <hidden> Date: 2002-08-23 09:34:35
On Fri, 2002-08-23 at 07:18, Dan Malek wrote:
Dr. Craig Hollabaugh wrote:
quoted
I'm curious ...
How many out there actually are compiling PPC code natively on a PowerPC Linux box for their embedded devices?
Me.
And I remember what you thought about people like me that tried to make
the cross compile environment going. Lucky you that I managed to delete
my old mbox otherwise I could repost some interesting mail :)
But it finally did work out OK and nowadays all you really need to now
is what parameters to give the configure script.
--
Kenneth Johansson
Ericsson AB Tel: +46 8 404 71 83
Borgafjordsgatan 9 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@etx.ericsson.se
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Jerry Van Baren <hidden> Date: 2002-08-23 12:56:40
At 05:39 PM 8/22/2002 -0600, Dr. Craig Hollabaugh wrote:
At 09:36 AM 8/22/2002 +0200, Marius Groeger wrote:
quoted
2. The "emulation" will never be 100%. Maybe 99%. Maybe 99.99%. That last
fraction can be a major PITA, because it is not obvious. To compile a
kernel you need a lot of tools with a lot of explicit and implicit twists
to them. It is just a gut feeling that I wouldn't want to rely on this,
if I don't have to. The native way just seems the better way to do it to
me.
Just because your running on Linux doesn't mean anything because your
duplicating
the environment for cross-compiling anyway. So what does it matter if
cygwin runs
the cross tools or if Linux runs them?
I'm curious ...
How many out there actually are compiling PPC code natively on a PowerPC
Linux box for their embedded devices?
If so, do you run the same development versions on your desktop?
How do you handle the FPU issues?
Craig
We've done native on an iMac and cross on X86 linux.
Additional problems with Cygwin, from my point of view, is that you will
always be trailing the mainstream development because the Cygwin tools are
based on the native linux toolsets rebuilt (perhaps with customizations) to
allow them to run under DOS. In addition, there are only a fraction as
many engineers using Cygwin vs. linux so your pool of "informed developers"
to ask questions of is much smaller. Perhaps both of those objections go
away if you pay for Cygwin support :-).
My limited experience with Cygwin is that it is like cutting with a dull
knife: it can get the job done, but you have to work harder and the results
are a little more ragged than they should be.
gvb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Dan Malek <hidden> Date: 2002-08-24 00:11:04
Kenneth Johansson wrote:
And I remember what you thought about people like me that tried to make
the cross compile environment going.
The only opinion I have changed is that people that can actually make
this work well (and I know of only a couple) have a special talent
and I really like them to hang around :-)
I guess when you work for a large company that will pay your salary regardless
of missing schedules and can only provide half-assed tools you have to
cobble together to make things work, you are both lucky and have my sympathy.
I don't have the patience or development time to create or debug my
development tools, they just have to work. I'm not using anything that
anyone else can't go out and purchase or download, and it continues to
baffle me why people won't take the easy route to developing software.
But it finally did work out OK and nowadays all you really need to now
is what parameters to give the configure script.
There is LOTS more to creating an easy to use and properly created set
of development tools than knowing some parameters to configure scripts.
Only a couple of people I know understand the magic, and it isn't documented.
I'm just going to rely on them to make my job easier :-)
Have fun!
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
From: Sangmoon Kim <hidden> Date: 2002-08-27 10:24:00
Hi,
I built a toolchain for ppc under cygwin about a year ago.
I used the Billgatliff's script(http://crossgcc.billgatliff.com/build-crossgcc.sh)
It failed to build glibc. So I copied glibc from a linux machine.
I've been using the toolchain, without any problem, for our custom MPC755 board, for about a year.
I recommand the Billgatliff's script, if you are going to make a tool chain for ppc under cygwin.
- Sangmoon Kim -
----- Original Message -----
From: "Dan Malek" <redacted>
To: "Kenneth Johansson" <redacted>
Cc: "Dr. Craig Hollabaugh" <redacted>; "Marius Groeger" <redacted>; "John Fisher" <redacted>; "Linuxppc embedded" <redacted>
Sent: Saturday, August 24, 2002 9:11 AM
Subject: Re: cygwin and embedded linux
Kenneth Johansson wrote:
quoted
And I remember what you thought about people like me that tried to make
the cross compile environment going.
The only opinion I have changed is that people that can actually make
this work well (and I know of only a couple) have a special talent
and I really like them to hang around :-)
I guess when you work for a large company that will pay your salary regardless
of missing schedules and can only provide half-assed tools you have to
cobble together to make things work, you are both lucky and have my sympathy.
I don't have the patience or development time to create or debug my
development tools, they just have to work. I'm not using anything that
anyone else can't go out and purchase or download, and it continues to
baffle me why people won't take the easy route to developing software.
quoted
But it finally did work out OK and nowadays all you really need to now
is what parameters to give the configure script.
There is LOTS more to creating an easy to use and properly created set
of development tools than knowing some parameters to configure scripts.
Only a couple of people I know understand the magic, and it isn't documented.
I'm just going to rely on them to make my job easier :-)
Have fun!
-- Dan