From: James Kosin <jkosin@intcomgrp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fwd: Re: U-Boot Compiling in CYGWIN environment
Date: Thu, 28 Jan 2010 12:56:25 -0500 [thread overview]
Message-ID: <4B61CFC9.1050808@intcomgrp.com> (raw)
Sorry, forgot to copy the list on this...
See below:
-------- Original Message --------
Subject: Re: [U-Boot] U-Boot Compiling in CYGWIN environment
Date: Thu, 28 Jan 2010 12:55:38 -0500
From: James Kosin <jkosin@intcomgrp.com>
To: Wolfgang Denk <wd@denx.de>
On 1/28/2010 12:35 PM, Wolfgang Denk wrote:
> Dear James Kosin,
>
> In message <4B61A431.6060307@intcomgrp.com> you wrote:
>
>> (2) I'm developing on a Windows system (don't laugh); but, I can't
>> easily change or add VMware to the picture.
>>
> Maybe you can use one of the many other existing solutions - CoLinux,
> VirtualBox, etc. etc.
>
>
> Best regards,
>
> Wolfgang Denk
>
>
Well, ....
Here is a patch I recently came up with.... granted it does work;
however, the code has started using static inline definitions in header
files which don't compile with the restriction of -ansi for the C flags
on CYGWIN.
The first line allows us to know the endian-ness of the machine, then I
define inline to get rid of the errors about using inline ... messy
produces a lot of warnings about static functions that are not called.
Then I define ulong as being unsigned long.
It fixes the compile for CYGWIN.
James K
--- Patch Below ---
diff --git a/include/compiler.h b/include/compiler.h
index 332618e..cd1e416 100644
--- a/include/compiler.h
+++ b/include/compiler.h
@@ -8,6 +8,12 @@
#include <stddef.h>
#ifdef USE_HOSTCC
+#if defined(__CYGWIN__)
+#include <endian.h>
+#define inline
+typedef unsigned long ulong;
+#endif
+
#if defined(__BEOS__) || \
defined(__NetBSD__) || \
reply other threads:[~2010-01-28 17:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B61CFC9.1050808@intcomgrp.com \
--to=jkosin@intcomgrp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.