From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: avr-gcc Date: Sat, 16 Apr 2016 21:55:52 +0200 Message-ID: <878u0dqqev.fsf@drakenvlieg.flower> 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> <87ega6shm2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1arWKD-0000QT-7l for guix-devel@gnu.org; Sat, 16 Apr 2016 15:56:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1arWK9-0000gF-88 for guix-devel@gnu.org; Sat, 16 Apr 2016 15:56:13 -0400 In-Reply-To: <87ega6shm2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 15 Apr 2016 23:10:45 +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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Andy Wingo , "guix-devel@gnu.org" Ludovic Court=C3=A8s writes: > Jan Nieuwenhuizen skribis: > >> Except for packages that need a native gcc to build tools during build >> time (CC_FOR_BUILD). For such packages (like Bash or Guile), >> standard-packages must include gcc again. Then, the build recipe's >> phases must be changed so that when cross compiling, the >> C_INCLUDE_PATH is moved into CPATH and C_INCLUDE_PATH is unset. >> That makes this solution even more unattractive, many changes >> to package recipe's could be needed. > > Right! That is really a bug, and I wonder why we didn=E2=80=99t catch it= before > (maybe because the libc=E2=80=99s are pretty much the same in the systems= we > were targeting?). > > I had actually worked around it in > e8e2e18b84eb8842a59be9bf7d49bb672260ae3a in one particular case. Ah, I see. > So the fix, as you suggest, is (1) to change > gcc-cross-environment-variables.patch to CROSS_ify the other environment > variables as well, and (2) to remove the unsetenv that was added in > e8e2e18b84eb8842a59be9bf7d49bb672260ae3a. Yes, that's the idea. And then also use CROSS_C_INCLUDE_PATH and C_INCLUDE_PATH in cross-base.scm, i.e., for the new libc and gcc cross builds. > Could you give it a try? :-) I'm looking into this and have some success, quite some things need to be rebuilt ;-) > Thanks for taking the time to explain! That's good to hear! Thanks for looking into this and providing information! Greetings, Jan --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.nl= =20=20