linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: John.Fisher@nec.com.au
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: cygwin and embedded linux
Date: Wed, 21 Aug 2002 16:54:12 +0200	[thread overview]
Message-ID: <3D63A994.EF67FC03@opensource.se> (raw)
In-Reply-To: 000301c248e8$9a2ce040$37d34c93@neca.nec.com.au


> Is anyone seriously trying to do embedded Linux development for power PC
> using Cygwin as the host?

I've designed a build-system for a customer, and I tried (just to see
how
much that worked ok) to build under Cygwin. Everything worked out ok
until
the system cross compiled glibc-2.1.3. Building glibc generated a error
message that meant something like you-have-bad-memory-on-your-system.
I tried to find the source of the problem with rebuilding and running
memtest86. But no success. But this was maybe a year ago.

The same system works great on Linux boxes.

That's my only experience.

But I have a box from Lynuxworks somewhere here (someone gave it to me)
and that box says that the build system is hosted on windows...

/ Magnus

John Fisher wrote:
>
> Is anyone seriously trying to do embedded Linux development for power PC
> using Cygwin as the host?
>
> I'm trying to get linux running on proprietary MPC850/860/8260 boards. I'll
> start with either the 850 or the 860 board as I'm more familiar with these
> processors than with the 8260.
>
> I have the Macraigor blackbird BDM interface for the MPC850/860. I have both
> an Agilent ethernet based probe and the Wind River Vision Probe II for the
> 8260.
>
> All boards will be running with plenty of flash and RAM: 16MB and 32MB
> respectively for both the 850 and 860 boards. They will be running with no
> disk drive, no monitor and a serial port on SCC3.
>
> I may have real time requirements, but this is yet to be determined.
>
> This is a learning exercise at this stage.
>
> John Fisher
> NEC Australia Pty Ltd
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-08-21 14:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21  7:58 cygwin and embedded linux John Fisher
2002-08-21 14:54 ` Magnus Damm [this message]
2002-08-21 15:54 ` Marius Groeger
2002-08-22  1:15   ` John Fisher
2002-08-22  3:20     ` Pete McCormick
2002-08-22  6:56     ` Wolfgang Denk
2002-08-23  0:05       ` Dr. Craig Hollabaugh
2002-08-22  7:36     ` Marius Groeger
2002-08-23 13:13       ` Marius Groeger
2002-08-22 11:00     ` Magnus Damm
2002-08-23 13:10       ` Jerry Van Baren
     [not found]     ` <Pine.LNX.4.40.0208220914420.2118-100000@mag.devdep.sysgo.d e>
2002-08-22 23:39       ` Dr. Craig Hollabaugh
2002-08-23  5:18         ` Dan Malek
2002-08-23  7:03           ` Dr. Craig Hollabaugh
2002-08-23  9:34           ` Kenneth Johansson
2002-08-24  0:11             ` Dan Malek
2002-08-27 10:24               ` Sangmoon Kim
2002-08-23  9:15         ` Magnus Damm
2002-08-23 12:56         ` Jerry Van Baren
2002-08-23  5:03     ` Dan Taylor
  -- strict thread matches above, loose matches on Subject: below --
2002-08-21 15:07 Steven Blakeslee
2002-08-22 13:06 Hihn Jason
2002-08-22 23:48 Kerl, John
2002-08-22 23:50 Kerl, John

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=3D63A994.EF67FC03@opensource.se \
    --to=damm@opensource.se \
    --cc=John.Fisher@nec.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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).