All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <mathstuf@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-05
Date: Tue, 9 Aug 2016 10:15:06 -0400	[thread overview]
Message-ID: <20160809141506.GA28979@megas.kitware.com> (raw)
In-Reply-To: <CAHXCMM+xOgCuMNHMSqj4tOP2jMGP7OPOLD1_x0_8HCgXb_h21g@mail.gmail.com>

On Sun, Aug 07, 2016 at 17:48:46 +0200, Samuel Martin wrote:
> It seems to be another error due to "-isystem
> $(STAGING_DIR)/usr/include" passed to g++ [1].
> 
> AFAICS, this is done by CMake when generating the flags.make files.
> Note that removing it from the CXX_INCLUDES variables in all generated
> flags.make prevent from triggering this error.
> 
> It is not clear to me whether it is a gcc-6.x bug or a CMake one.
> According to fedora developers, this is not a gcc-6 bug [2].
> Ben, do you have any idea?

It might be that CMake is having trouble determining the paths that the
compiler uses by default? It should exclude any such directories from
the -I setup (though -isystem may change this behavior). CMake builds up
this variable:

    https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_IMPLICIT_INCLUDE_DIRECTORIES.html

based on the platform. It prefixes these with the value of CMAKE_SYSROOT
to create the list of implicit directories it ignores when building up
-I lines. Is CMAKE_SYSROOT not set properly?

> Ben, I have not opened any ticket yet, nor checked if a similar one is
> already opened. Do you need more details?

Building with VERBOSE=1 would help since it would show the actual
command lines being used. It may also help to move over to the
cmake-developers list to reach more CMake developers:

    https://cmake.org/mailman/listinfo/cmake-developers

--Ben

  reply	other threads:[~2016-08-09 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-05 Thomas Petazzoni
2016-08-07  9:26 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-07 11:46   ` Waldemar Brodkorb
2016-08-09 10:03     ` Thomas Petazzoni
2016-08-07 14:33   ` Frank Hunleth
2016-08-07 15:48   ` Samuel Martin
2016-08-09 14:15     ` Ben Boeckel [this message]
2016-08-17 21:18       ` Samuel Martin
2016-08-08 15:56   ` Vlad Zakharov
2016-08-08 20:34     ` Thomas Petazzoni
2016-08-11 10:43       ` Vlad Zakharov
2016-08-09 13:27   ` gwenhael.goavec
2016-08-09 13:41     ` Thomas Petazzoni

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=20160809141506.GA28979@megas.kitware.com \
    --to=mathstuf@gmail.com \
    --cc=buildroot@busybox.net \
    /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.