public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] building cross_tools, _POSIX_C_SOURCE and _XOPEN_SOURCE are redefined
Date: Mon, 20 Mar 2017 07:41:45 +0100	[thread overview]
Message-ID: <58CF79A9.8000005@denx.de> (raw)
In-Reply-To: <alpine.LFD.2.20.1703150359110.10061@localhost.localdomain>

Hello Robert,

Am 15.03.2017 um 09:02 schrieb Robert P. J. Day:
>
>    to build cross_tools, i ran:
>
>    $ make sandbox_defconfig
>    $ make cross_tools
>
> and while it appeared to work, i got:
>
> ... snip ...
>
> LDFLAGS="" python ./lib/libfdt/setup.py \
> 	"-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer    -DCONFIG_FIT_SIGNATURE -include ./include/libfdt_env.h -idirafterinclude -idirafter./arch/sandbox/include -I./lib/libfdt -I./tools -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/include/python2.7/pyconfig.h:6:0,
>                   from /usr/include/python2.7/Python.h:8,
>                   from tools/libfdt_wrap.c:143:
> /usr/include/python2.7/pyconfig-64.h:1203:0: warning: "_POSIX_C_SOURCE" redefined
>   #define _POSIX_C_SOURCE 200112L
>   ^
> In file included from /usr/include/stdint.h:25:0,
>                   from /usr/lib/gcc/x86_64-redhat-linux/5.3.1/include/stdint.h:9,
>                   from ././include/compiler.h:19,
>                   from ././include/libfdt_env.h:12,
>                   from <command-line>:0:
> /usr/include/features.h:225:0: note: this is the location of the previous definition
>   # define _POSIX_C_SOURCE 200809L
>   ^
> In file included from /usr/include/python2.7/pyconfig.h:6:0,
>                   from /usr/include/python2.7/Python.h:8,
>                   from tools/libfdt_wrap.c:143:
> /usr/include/python2.7/pyconfig-64.h:1225:0: warning: "_XOPEN_SOURCE" redefined
>   #define _XOPEN_SOURCE 600
>   ^
> In file included from /usr/include/stdint.h:25:0,
>                   from /usr/lib/gcc/x86_64-redhat-linux/5.3.1/include/stdint.h:9,
>                   from ././include/compiler.h:19,
>                   from ././include/libfdt_env.h:12,
>                   from <command-line>:0:
> /usr/include/features.h:166:0: note: this is the location of the previous definition
>   # define _XOPEN_SOURCE 700
>   ^
>
>
>    not sure if that concerns anyone enough to want to tweak it.

I stumbled also over this, but did not find time to look into it...

So, if you have time for fixing it, that would be nice ;-)

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

      parent reply	other threads:[~2017-03-20  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  8:02 [U-Boot] building cross_tools, _POSIX_C_SOURCE and _XOPEN_SOURCE are redefined Robert P. J. Day
2017-03-17 14:31 ` Tom Rini
2017-03-28  9:51   ` Robert P. J. Day
2017-03-28 11:36     ` Jelle van der Waa
2017-03-20  6:41 ` Heiko Schocher [this message]

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=58CF79A9.8000005@denx.de \
    --to=hs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox