From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Wingo Subject: Re: avr-gcc Date: Fri, 15 Apr 2016 15:13:21 +0200 Message-ID: <878u0fypzi.fsf@igalia.com> References: <87wptgmyv1.fsf@elephly.net> <87twoks459.fsf@gnu.org> <87a8qbr2mb.fsf@gnu.org> <87ziy8g3bp.fsf@gnu.org> <87a8kxfdgc.fsf@gnu.org> <87h9f4spw3.fsf@drakenvlieg.flower> <87twj4m92o.fsf@gnu.org> <878u0fs38f.fsf@drakenvlieg.flower> <87potrz1nh.fsf@igalia.com> <874mb3rqh4.fsf@drakenvlieg.flower> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60704) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ar3Yy-0000mo-Kt for guix-devel@gnu.org; Fri, 15 Apr 2016 09:13:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ar3Yt-0005NQ-Q7 for guix-devel@gnu.org; Fri, 15 Apr 2016 09:13:32 -0400 In-Reply-To: <874mb3rqh4.fsf@drakenvlieg.flower> (Jan Nieuwenhuizen's message of "Fri, 15 Apr 2016 14:44:39 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jan Nieuwenhuizen Cc: "guix-devel@gnu.org" Hi :) On Fri 15 Apr 2016 14:44, Jan Nieuwenhuizen writes: > Andy Wingo writes: > >> Or is there some special logic which is applying to CPATH which is not >> applying to C_INCLUDE_PATH? > > Ah, yes; CPATH is not used when cross building, instead CROSS_CPATH is > used. Ah, I see. I guess that's the essential difference. >> Basically in Guix we should, IMO, always be working on C_INCLUDE_PATH >> and friends, and never on CPATH. > > I'm guessing that could work; would could try to change the above patch > (in gcc-cross-environment-variables.patch) to handle C*_INCLUDE_PATH and > introduce CROSS_C*_INCLUDE_PATH. > > I just wonder if there was another reason for cross builds to choose > CPATH/CROSS_CPATH instead of C_*INCLUDE_PATH. Apart maybe from the > fact that we would need to handle all `*' where CPATH works for all > languages. Yeah let's give this a try instead. Probably we should support CROSS_ variants of all of these include paths: CPATH, C_INCLUDE_PATH, and so on. I admit I don't understand why the CROSS_ paths are needed. But I haven't looked into it and if I don't need to know, I am happy to remain ignorant :) Happy hacking, Andy ps. Thank you for all of your work here, Jan!