From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cross-compiling U-Boot on Mac OS X -- can't find crc32.c?
Date: Wed, 20 May 2009 10:41:09 -0400 [thread overview]
Message-ID: <4A141685.3090306@ge.com> (raw)
In-Reply-To: <ed82fe3e0905200733m210b9e23x6269d49c0d589164@mail.gmail.com>
Timur Tabi wrote:
> On Wed, May 20, 2009 at 12:31 AM, Wolfgang Denk <wd@denx.de> wrote:
>
>> It's you who has OS X, and who has a problem. Only when Ah itchez, Ah
>> scratchez.
>
> Just so I'm clear on this, you're saying that you're not really
> concerned about how well U-Boot works for other people?
No, people that aren't running OS X cannot debug problems that happen
when running on OS X.
You wrote:
> Well, I tried to fix it, but I can't figure it out. I just don't
> understand why it's so broken. The errors I get are so confusing, and
> I can't figure out what the Makefile is doing when it fails. So I
> give up.
followed by:
> Wolfgang, I think you seriously need to revamp your build process.
> The kernel is orders of magnitude more complex than U-Boot, and yet I
> can build it just fine on OS X.
That sounds like you want Wolfgang to fix a problem he doesn't have and
cannot reproduce, since he isn't running OS X (to the best of my knowledge).
<http://xkcd.com/583/>
gvb
next prev parent reply other threads:[~2009-05-20 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 23:30 [U-Boot] Cross-compiling U-Boot on Mac OS X -- can't find crc32.c? Timur Tabi
2009-05-02 0:10 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-04 13:27 ` Timur Tabi
2009-05-05 0:47 ` Mike Frysinger
2009-05-05 15:33 ` Timur Tabi
2009-05-20 1:38 ` Timur Tabi
2009-05-20 5:31 ` Wolfgang Denk
2009-05-20 14:33 ` Timur Tabi
2009-05-20 14:41 ` Jerry Van Baren [this message]
2009-05-20 14:52 ` Timur Tabi
2009-05-30 0:23 ` Mike Frysinger
2009-05-02 5:49 ` Wolfgang Denk
2009-05-02 23:02 ` Timur Tabi
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=4A141685.3090306@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.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