From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Analysis of build results
Date: Mon, 17 Aug 2020 11:40:11 +0200 [thread overview]
Message-ID: <20200817114011.5ff58f12@windsurf.home> (raw)
In-Reply-To: <20200817111940.004fc88d@x230_1.trabucayre.com>
Hello,
On Mon, 17 Aug 2020 11:19:40 +0200
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:
> > > mips | gr-osmosdr-0.2.0 | NOK | http://autobuild.buildroot.net/results/3bb8d678aaa782b70c14a8f9cd3e1df2e55bc613 |
> >
> > mips-linux-gnu-g++: ERROR: unsafe header/library path used in cross-compilation: '-isystem' '/usr/include'
> > mips-linux-gnu-g++: ERROR: unsafe header/library path used in cross-compilation: '-isystem' '/usr/include'
> >
> > Gwenhael, could you take care of this, at least do some preliminary
> > analysis to find where this bogus -isystem invocation comes from ?
> >
> I have, by the past, often and again now, searched for the solution. Seems a problem with cmake:
> debian stable with cmake 3.13.4 -> fail
> debian stable with cmake provided by buildroot (force support/dependencies/check-host-cmake.mk) -> success
>
> I search for a way to have cmake more verbose to determine where the -isystem is added...
Do you know which distro/version uses cmake 3.13.4 so that we can try
to reproduce the issue ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-17 9:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 8:01 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-08-14 Thomas Petazzoni
2020-08-15 22:09 ` [Buildroot] [autobuild.buildroot.net] Analysis of build results Thomas Petazzoni
2020-08-15 22:14 ` Thomas Petazzoni
2020-08-17 9:19 ` Gwenhael Goavec-Merou
2020-08-17 9:40 ` Thomas Petazzoni [this message]
2020-08-17 9:51 ` Gwenhael Goavec-Merou
2020-08-17 12:18 ` Asaf Kahlon
2020-08-17 12:52 ` Thomas Petazzoni
2020-08-17 20:54 ` Peter Seiderer
2020-08-17 21:30 ` Thomas Petazzoni
2020-08-17 21:57 ` Peter Seiderer
2020-08-17 21:15 ` Peter Seiderer
2020-08-17 21:43 ` Romain Naour
2020-08-19 11:47 ` Fabrice Fontaine
2020-08-19 20:31 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2020-08-19 21:33 ` Alexey Brodkin
2020-09-11 8:39 ` Thomas Petazzoni
2020-10-02 15:16 ` Alexey Brodkin
2020-10-06 18:57 ` Arnout Vandecappelle
2020-08-20 9:22 ` [Buildroot] " Frank Vanbever
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=20200817114011.5ff58f12@windsurf.home \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox