All of lore.kernel.org
 help / color / mirror / Atom feed
From: George G. Davis <davis_g@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Unable to compile the U-boot-0.4.8 version for OMAP1610/1510/smdk2410
Date: Fri, 12 Sep 2003 10:17:49 -0400	[thread overview]
Message-ID: <3F61D58D.7090308@comcast.net> (raw)
In-Reply-To: <20030912132824.DB953C59E4@atlas.denx.de>



Wolfgang Denk wrote:
> Dear Rahul,
> 
> in message <002701c37923$8fc51520$d253579d@a0875497> you wrote:
> 
>>I am not able to compile the new u-boot tar ball i.e. u-boot-0.4.8,
>>u-boot-0.4.7 compiles fine .
>>I got the following error message after
>>make omap1610inn_config
>>make command
> 
> ...
> 
>>/usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:43: parse error
>>before
>>`__gnuc_va_list'
>>/usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:43: warning: data
>>defin
>>ition has no type or storage class
>>/usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:110: parse error
>>before
>> `va_list'  "
>>
>>can anybody tell me what is the problem.
> 
> 
> This means that your cross compiler is  broken.  The  cross  compiler
> must  NEVER  reference  include  files  from  the  native development
> system.

Um, it's not the cross compiler that's doing it in this case. gccincdir
is not defined for drivers/sk98lin. Try the attached patch. It WFM/YMMV.

--
Regards,
George


> 
> Best regards,
> 
> Wolfgang Denk
> 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20030912/f44bba7f/attachment.txt 

  reply	other threads:[~2003-09-12 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 11:46 [U-Boot-Users] Unable to compile the U-boot-0.4.8 version for OMAP1610/1510/smdk2410 Rahul Shanbhag
2003-09-12 13:28 ` Wolfgang Denk
2003-09-12 14:17   ` George G. Davis [this message]
2003-09-12 16:13     ` Wolfgang Denk
2003-09-12 17:26       ` George G. Davis

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=3F61D58D.7090308@comcast.net \
    --to=davis_g@comcast.net \
    --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.