From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: rfh: mingw guile.exe stalled by impact of 28dc10a4 Date: Sun, 05 Jun 2016 22:26:08 +0200 Message-ID: <874m974c2n.fsf@gnu.org> References: <87eg8bu9gu.fsf@gnu.org> <87oa7fpf71.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]:52330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9ed1-0007bs-C6 for guix-devel@gnu.org; Sun, 05 Jun 2016 16:26:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b9ecx-0008Ld-4H for guix-devel@gnu.org; Sun, 05 Jun 2016 16:26:34 -0400 In-Reply-To: <87oa7fpf71.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 05 Jun 2016 22:13:06 +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: guix-devel@gnu.org Ludovic Court=C3=A8s writes: > Hmm the above commit normally cannot trigger anything since it simply > modifies =E2=80=9Cbuild-side=E2=80=9D code (that is, it does not change t= he inputs of > packages; it just changes the content of the build program.) Hmm, could it be then that everything that this commits seems to trigger has an already sucessfully built version in the store that matches the description without the commit (cross x86_64 gcc, bootrap gcc etc). In that case, it "simply" breaks cross gcc and bootstrap gcc? However, I fail to see how this happens. And "tar" missing In execvp of tar: No such file or directory during builder for `/gnu/store/m6gq2xz5kd3vn4zm1i0i6j0immlgyhmg-make-boot0-4.1= .drv' failed with exit code 1 cannot build derivation `/gnu/store/1fjnm2x2az4z4qaz3bad5p5zbygf5wqs-gc= c-cross-boot0-4.9.3.drv':=20 I figured this all could/should not be the result of this commit? > Are you sure that reverting this commit solves the problem? Yes, reverting it produces the cross-built readline. > Maybe we=E2=80=99re entering a cross-build context with =E2=80=98%current= -target-system=E2=80=99 > set to =E2=80=98x86_64-linux-gnu=E2=80=99 at some point? Yes, I'm pretty sure that's what happens. Greetings, Jan --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.nl= =20=20