linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
Cc: "Dr. Craig Hollabaugh" <craig@hollabaugh.com>,
	Marius Groeger <mag@sysgo.de>,
	John Fisher <John.Fisher@nec.com.au>,
	Linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: cygwin and embedded linux
Date: Fri, 23 Aug 2002 20:11:04 -0400	[thread overview]
Message-ID: <3D66CF18.5040801@embeddededge.com> (raw)
In-Reply-To: 1030095276.2481.230.camel@spawn


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/

  reply	other threads:[~2002-08-24  0:11 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
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 [this message]
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=3D66CF18.5040801@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=John.Fisher@nec.com.au \
    --cc=craig@hollabaugh.com \
    --cc=kenneth.johansson@etx.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mag@sysgo.de \
    /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).