All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle van der Waa <jelle@vdwaa.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] building cross_tools, _POSIX_C_SOURCE and _XOPEN_SOURCE are redefined
Date: Tue, 28 Mar 2017 13:36:51 +0200	[thread overview]
Message-ID: <20170328113650.GB2920@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1703280550010.30434@uk63952.mitel.com>

On 03/28/17 at 05:51am, Robert P. J. Day wrote:
> On Fri, 17 Mar 2017, Tom Rini wrote:
> 
> > On Wed, Mar 15, 2017 at 04:02:20AM -0400, Robert P. J. Day wrote:
> > >                  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.
> >
> > This is the second report I've gotten about this.  But, we don't set any
> > of those things directly.  It's something related to the python install
> > you have.  Can you please dig a bit more?  Thanks!
> 
>   if no one else has figured out what is going on here, i'll try
> poking around this weekend. but AFAIK, i haven't done anything out of
> the ordinary with my python installation.

The issue is that Python.h has to be included before the rest of the
header files. As can be read in the Python documentation:

"Note Since Python may define some pre-processor definitions which
affect the standard headers on some systems, you must include Python.h
before any standard headers are included." [1]

I have no idea how to achieve this though in u-boot.

[1] https://docs.python.org/3/c-api/intro.html#includes

-- 
Jelle van der Waa

  reply	other threads:[~2017-03-28 11:36 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 [this message]
2017-03-20  6:41 ` Heiko Schocher

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=20170328113650.GB2920@gmail.com \
    --to=jelle@vdwaa.nl \
    --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.