From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:55567) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ihtgy-0001se-2U for guix-patches@gnu.org; Thu, 19 Dec 2019 06:10:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ihtgw-0004A8-Pp for guix-patches@gnu.org; Thu, 19 Dec 2019 06:10:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38339) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ihtgw-00048B-ID for guix-patches@gnu.org; Thu, 19 Dec 2019 06:10:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ihtgw-0001rc-88 for guix-patches@gnu.org; Thu, 19 Dec 2019 06:10:02 -0500 Subject: [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <87tv6qoank.fsf@gnu.org> <87sgm4m9fu.fsf@gnu.org> <87v9r0arni.fsf@gnu.org> <87y2vqdjwz.fsf@gnu.org> <87y2viyb2a.fsf@gnu.org> <87o8w9s284.fsf@gnu.org> <878sncm5od.fsf@gnu.org> <87o8w5gs6m.fsf@gnu.org> Date: Thu, 19 Dec 2019 12:08:54 +0100 In-Reply-To: <87o8w5gs6m.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 18 Dec 2019 23:55:13 +0100") Message-ID: <87y2v8tvw9.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Jan Nieuwenhuizen Cc: Timothy Sample , 38390@debbugs.gnu.org Hi! Jan Nieuwenhuizen skribis: > Good news. bash-mesboot0 now compiles with either gash+gash-core-utils, > or with bash-mesboot0. > > Gash' "test -L FILE" used to crash on non-existing files, not sure why > that made configure hang; but that's how I found and fixed it. > > The problem with bash-mesboot0 turned out to be a Mes C Library problem, > related to buffered reads. Buffered reads were introduced when working > on the Hurd. > > Not clearing the read buffer on lseek, when lseek is not allowed (bash > uses the same: lseek (FD, 0, SEEK_CUR) to find out if it may seek), > fixes the problem. That took me a couple of days to find, but very > happy=20 Woow, wild! Great that you found out! Thank you, Ludo=E2=80=99.