From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#30756: GCC >= 6 '-isystem' and C_INCLUDE_PATH behavior changed, breaking Date: Tue, 04 Feb 2020 12:28:22 +0100 Message-ID: <874kw6zj55.fsf@gnu.org> References: <87y2u3qh8b.fsf@gnu.org> <87r1zulsgc.fsf@gmail.com> <87sgkaik08.fsf@gnu.org> <878sm0kx8b.fsf@gmail.com> <87wo9hnbp9.fsf@gnu.org> <87blqg2gg5.fsf@gnu.org> <87blqfmlhh.fsf@devup.no> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52709) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iywO7-0006rT-I2 for bug-guix@gnu.org; Tue, 04 Feb 2020 06:29:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iywO6-0003dr-Jq for bug-guix@gnu.org; Tue, 04 Feb 2020 06:29:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:36703) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iywO5-0003bk-Qs for bug-guix@gnu.org; Tue, 04 Feb 2020 06:29:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iywO5-0002Yo-Lx for bug-guix@gnu.org; Tue, 04 Feb 2020 06:29:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87blqfmlhh.fsf@devup.no> (Marius Bakke's message of "Mon, 03 Feb 2020 22:03:54 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Marius Bakke Cc: reza.housseini@gmx.ch, 30756@debbugs.gnu.org, Maxim Cournoyer , Reza Housseini Hello! Marius Bakke skribis: > The patch looks great to me. Love how simple your solution was. The > #include_next issue be confusing and frustrating even for seasoned Guix > developers, so I'm all for getting it in ASAP. Great. We=E2=80=99ll make new friends with this patch, I can tell you. ;-) > Can you check whether (gnu packages cross-base) can be adjusted in the > same vein? I.e. go back to CROSS_C_INCLUDE_PATH & co, and dropping the > 'treat-glibc-as-system-header' phase from "cross-gcc-arguments". Yes, though probably as a separate patch, if you don=E2=80=99t mind, because cross-base is kinda orthogonal. I=E2=80=99ve started looking at places where we manually fiddle with CPATH/C_INCLUDE_PATH and found some more in build systems. But then, there are also quite a few individual packages that fiddle with it, so it=E2=80=99ll certainly take some time before we find and address each of t= hese. Related to that, I=E2=80=99ll be posting a patch that clarifies search path handling in commencement.scm=E2=80=94not a prerequisite, but a nice bonus I= MO. Thanks, Ludo=E2=80=99.