From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] libfdt/fdt_ro.c build issues...
Date: Tue, 26 Aug 2008 22:04:30 -0400 [thread overview]
Message-ID: <48B4B62E.5000301@gmail.com> (raw)
In-Reply-To: <20080827001315.35445248C3@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Kumar,
>
> there are build problems with libfdt/fdt_ro.c :
>
> ...
> 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
> ...
>
> ...dor all boards.
>
> If you have time, could you please have a look?
>
> Best regards,
>
> Wolfgang Denk
??? 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.
libfdt/fdt_ro.c includes...
#ifndef USE_HOSTCC
#include <fdt.h>
#include <libfdt.h>
#else
#include "fdt_host.h"
#endif
and then fdt_host.h includes libfdt.h...
/* Make sure to include u-boot version of libfdt include files */
#include "../include/fdt.h"
#include "../include/libfdt.h"
#include "../include/fdt_support.h"
Best regards,
gvb
next prev parent reply other threads:[~2008-08-27 2:04 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 [this message]
2008-08-27 7:42 ` Wolfgang Denk
2008-08-27 8:04 ` Wolfgang Denk
2008-08-27 11:42 ` JerryVanBaren
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=48B4B62E.5000301@gmail.com \
--to=gvb.uboot@gmail.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.