All of lore.kernel.org
 help / color / mirror / Atom feed
From: JerryVanBaren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] libfdt/fdt_ro.c build issues...
Date: Wed, 27 Aug 2008 07:42:48 -0400	[thread overview]
Message-ID: <48B53DB8.5040904@ge.com> (raw)
In-Reply-To: <20080827080448.315CA242FE@gemini.denx.de>

Wolfgang Denk wrote:
> Dear Jerry Van Baren,
> 
> In message <48B4B62E.5000301@gmail.com> you wrote:
>>> ...
>>> tools/fdt_ro.c: In function 'fdt_path_offset':
>>> tools/fdt_ro.c:158: warning: implicit declaration of function 'fdt_getprop_namelen'
>>> tools/fdt_ro.c:158: warning: assignment makes pointer from integer without a cast
>>> tools/fdt_ro.c: At top level:
>>> tools/fdt_ro.c:281: error: conflicting types for 'fdt_getprop_namelen'
>>> tools/fdt_ro.c:158: error: previous implicit declaration of 'fdt_getprop_namelen' was here
>>> ...
> ...
> 
>> ??? I'm not seeing this, even with a fresh pull from the u-boot repository.
>>
>> The function is declared in include/libfdt.h, properly in my copy.

(from your previous email):

> It seems it happens only for out-of-tree builds  (which is my standard
> mode of operation).

Yes, after I hit "send" and thought about the "../include", I had a bad 
feeling that that was the problem.

> The problem comes from tools/fdt_host.h which includes:
> 
> 	/* Make sure to include u-boot version of libfdt include files */
> 	#include "../include/fdt.h"
> 	#include "../include/libfdt.h"
> 	#include "../include/fdt_support.h"

There has to be a better way than the USE_HOSTCC / #include "fdt_host.h" 
(with a "up & over" relative path) mechanism.  Unfortunately, I don't 
have any good ideas at the moment.

What we really need is $(obj)include instead of "../include", but that 
is crossing the make $(obj) and the C preprocessor.  We could do it by 
running sed on fdt_host.h, but that wouldn't be a better way, just ugly.

[snip]

> Hm... not sure how to fix this.

Ditto.  :-(

> Best regards,
> 
> Wolfgang Denk

...thinking...
gvb
(...but don't expect much this weekend, it is Labor Day weekend in the 
USofA, the traditional last "hurrah" of summer).

  reply	other threads:[~2008-08-27 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  0:13 [U-Boot] libfdt/fdt_ro.c build issues Wolfgang Denk
2008-08-27  2:04 ` Jerry Van Baren
2008-08-27  7:42   ` Wolfgang Denk
2008-08-27  8:04   ` Wolfgang Denk
2008-08-27 11:42     ` JerryVanBaren [this message]
2008-09-06 21:21       ` Wolfgang Denk
2008-09-08  4:10         ` [U-Boot] [PATCH] Fix out-of-tree tools/fdt build Jerry Van Baren
2008-09-08  4:28           ` Jerry Van Baren

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=48B53DB8.5040904@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 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.