From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 17 Aug 2020 11:40:11 +0200 Subject: [Buildroot] [autobuild.buildroot.net] Analysis of build results In-Reply-To: <20200817111940.004fc88d@x230_1.trabucayre.com> References: <20200815080146.EBD3186EA1@fraxinus.osuosl.org> <20200816000914.5ad801d9@windsurf.home> <20200817111940.004fc88d@x230_1.trabucayre.com> Message-ID: <20200817114011.5ff58f12@windsurf.home> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Mon, 17 Aug 2020 11:19:40 +0200 Gwenhael Goavec-Merou 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