linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: cross-compiling under cygwin?
Date: Fri, 8 Apr 2005 14:35:49 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0504081434050.15953@localhost.localdomain> (raw)
In-Reply-To: <e6dbd8188d62839f349bec5a4cd0b352@embeddededge.com>

On Fri, 8 Apr 2005, Dan Malek wrote:

>
> On Apr 8, 2005, at 10:13 AM, Robert P. J. Day wrote:
>
> >   i've just had a request from a colleague who wants to do all the
> > cross-compilation for our 8xx board on a windows box, rather than
> > linux.

> Just remember there is lots more to building and developing than
> compiling a kernel.  In addition to the compiler, you need lots of
> support tools.  Once you get a kernel, you have to create some kind
> of file system, of course NFS won't work on Windows, creating a
> ramdisk without a loopback device and file system support is quite a
> challenge, too.

a lot of that was part of the conversation.  i suspect i may have to
be more persuasive.  something involving a blunt instrument, perhaps.

> I don't understand why you wouldn't want to develop on a Linux (or
> at least Unix) host, since you need those skills and environment for
> the target.  Do they just like impossible challenges in their way to
> getting real work done? :-)

i'm going to assume that was rhetorical. :-)

rday

  reply	other threads:[~2005-04-08 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 14:13 cross-compiling under cygwin? Robert P. J. Day
2005-04-08 14:46 ` Tom Rini
2005-04-08 16:49 ` Wolfgang Denk
2005-04-08 16:52   ` Robert P. J. Day
2005-04-08 17:57 ` Patrick Huesmann
2005-04-08 18:32 ` Dan Malek
2005-04-08 18:35   ` Robert P. J. Day [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-08 15:24 Steven Blakeslee
2005-04-08 18:48 Howard, Marc
2005-04-08 21:17 ` Dan Malek
2005-04-10 16:59 ` Wolfgang Denk
2005-04-11 18:30 Howard, Marc

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=Pine.LNX.4.61.0504081434050.15953@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=dan@embeddededge.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;
as well as URLs for NNTP newsgroup(s).