U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] build mkimage warning
Date: Wed, 22 Feb 2017 10:22:46 -0500	[thread overview]
Message-ID: <20170222152246.GP27120@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmU9TQ8G_fo+yXne9LT11E0pkJwrBYhLcp3kOu1ne7Uq5w@mail.gmail.com>

On Wed, Feb 22, 2017 at 07:21:12PM +0800, Bin Meng wrote:
> Hi Tom, Simon,
> 
> With latest main branch, I see some warnings when building mkimage:
> 
>   HOSTLD  tools/mkimage
> LDFLAGS="" python ./lib/libfdt/setup.py \
>                 "-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
> -include ./include/libfdt_env.h -idirafterinclude
> -idirafter./arch/x86/include -I./lib/libfdt -I./tools
> -DCONFIG_SYS_TEXT_BASE=0xfff00000 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES
> -D_GNU_SOURCE " lib/libfdt/fdt.c lib/libfdt/fdt_ro.c
> lib/libfdt/fdt_rw.c lib/libfdt/fdt_strerror.c lib/libfdt/fdt_wip.c
> lib/libfdt/fdt_region.c lib/libfdt/fdt_sw.c tools/libfdt_wrap.c
> In file included from /usr/local/include/python2.7/Python.h:8,
>                  from tools/libfdt_wrap.c:125:
> /usr/local/include/python2.7/pyconfig.h:1193:1: warning:
> "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/stdint.h:26,
>                  from ././include/compiler.h:19,
>                  from ././include/libfdt_env.h:12,
>                  from <command-line>:0:
> /usr/include/features.h:162:1: warning: this is the location of the
> previous definition
> In file included from /usr/local/include/python2.7/Python.h:8,
>                  from tools/libfdt_wrap.c:125:
> /usr/local/include/python2.7/pyconfig.h:1215:1: warning:
> "_XOPEN_SOURCE" redefined
> In file included from /usr/include/stdint.h:26,
>                  from ././include/compiler.h:19,
>                  from ././include/libfdt_env.h:12,
>                  from <command-line>:0:
> /usr/include/features.h:164:1: warning: this is the location of the
> previous definition
> mv _libfdt.so tools/_libfdt.so

How did you configure your local python2.7 install? Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170222/2cf0d6a2/attachment.sig>

  reply	other threads:[~2017-02-22 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 11:21 [U-Boot] build mkimage warning Bin Meng
2017-02-22 15:22 ` Tom Rini [this message]
2017-02-28  9:19   ` Bin Meng

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=20170222152246.GP27120@bill-the-cat \
    --to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox