All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems Building u-boot-1.3.1
Date: Thu, 13 Dec 2007 09:10:20 +0100	[thread overview]
Message-ID: <87abof582b.fsf@denx.de> (raw)
In-Reply-To: <8CA0B189597A91E-560-6E3D@MBLK-M30.sysops.aol.com> (raptorbrino@aim.com's message of "Wed, 12 Dec 2007 15:56:21 -0500")

raptorbrino at aim.com writes:

> I'm having a problem building u-boot-1.3.1.  It complains when using the
> host compiler to compile sha1.c because it doesn't know what the data 
> type
> __u64 is.  This datatype is defined in u-boot/include/asm/types.h.  
> However,
> I'm using cygwin, and it has the file /usr/include/asm/types.h.  The 
> types.h
> file in cygwin does not define __u64.  Because the compile uses the flag
> -idirafter, the cygwin types.h is used in the include, hence an unkown
> symbol compile error.  I fixed this problem in my local build by adding 
> the
> flag -ansi to CPPFLAGS in tools/makefile.  Is that appropriate or would 
> you
> recommend fixing it another way??

I would recommend fixing it by using a nice Linux system instead of
Win$, but thats just me...

Best regards

Markus Klotzbuecher

--
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de

  reply	other threads:[~2007-12-13  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 20:56 [U-Boot-Users] Problems Building u-boot-1.3.1 raptorbrino at aim.com
2007-12-13  8:10 ` Markus Klotzbücher [this message]
2007-12-13 18:51   ` raptorbrino at aim.com
2007-12-13 18:58     ` Wolfgang Denk
2007-12-13 19:55     ` Ben Warren
  -- strict thread matches above, loose matches on Subject: below --
2007-12-13 21:00 raptorbrino at aim.com
2007-12-13 22:07 ` Wolfgang Denk
2007-12-14  0:36   ` raptorbrino at aim.com
2007-12-14  2:23   ` raptorbrino at aim.com
2008-01-03 18:29     ` Jon Loeliger
2008-01-09 14:07     ` Wolfgang Denk

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=87abof582b.fsf@denx.de \
    --to=mk@denx.de \
    --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.