From debbugs-submit-bounces@debbugs.gnu.org Tue Dec 15 19:45:11 2020 Received: (at 45165) by debbugs.gnu.org; 16 Dec 2020 00:45:11 +0000 Received: from localhost ([127.0.0.1]:59482 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kpKwJ-0006Ow-I4 for submit@debbugs.gnu.org; Tue, 15 Dec 2020 19:45:11 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:54043) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kpKwH-0006Oe-Jm for 45165@debbugs.gnu.org; Tue, 15 Dec 2020 19:45:10 -0500 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 370CB5C0126 for <45165@debbugs.gnu.org>; Tue, 15 Dec 2020 19:45:04 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 15 Dec 2020 19:45:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=carldong.me; h= from:content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm2; bh=+UZs/8eMvX Z3NpIf5rpZN+njt2cQWGiSlDslHcIVb50=; b=BZDFlzNUiBRFFdp5SnrwvDii8r 0s4o/Ld4O9PgysXRfu2tyFuMtaK79U4fgOjEz0VwUWdVrBndDkdHdki5TJ4erUFP LYEPIKT75AQsA6B6BmU6n7c9edVt+Mxxt3p8HtxBLIpI6ADOvx8nl4Sj1seIw4Pi Lh3X0D5IBxgI+Afs2pmNZBJvdX8yByqy2+FJM6iIuA9HufOgJPgx//WkAzWo09HI mydDiROCDUeMr1dBay9ApEUp6QHvX3cEFxHHabJBi8OzV7lCZdwX5xHUhby6FEl5 4Lmr8fHvNzsm6IJGedly1g077IuvBKWJtvgUFGja1YOttQUBls5bVcpfvf/w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=+UZs/8eMvXZ3NpIf5rpZN+njt2cQWGiSlDslHcIVb 50=; b=G+4zQzr+O3IiROtj66g8GefDCzMw1eUUp0b/wn/87Wr1RtPhLRR3FyTR8 BDn5hwPbbBaxiaaocJfCI8oRQ5FVQD01K8KEVmVFRbKQB4Xf0ICr5KY67Y8gsUGj EKo4IpjgBCe2fQSdJCutdkVMtyrqxZgG81XIaV+6yBnHhnEJq+LlKm+AznE4F1ul YlkUhWzhCjX9Qe4UPXqoQEmLqKN4uqtBFZbraGoQzq+DwT2rqq4pNZ5QHV8aCXKV GKun/74xm5cq5QkbAdqdjleFJSdCQ1Zyjeg2r94GxEOvF0MaVQqo04YY1K0uREpA ruwhovtYcdwS5U/VLwB3i+qhfDPiA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeluddgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhtgfgggfuffhfvfgjkffosehtqh hmtdhhtdejnecuhfhrohhmpeevrghrlhcuffhonhhguceotghonhhtrggtthestggrrhhl ughonhhgrdhmvgeqnecuggftrfgrthhtvghrnheptdeugffgueetgeefjeffhedvteetke egtedtvdfgvdelleevgfethfeiffffveeinecuffhomhgrihhnpehmohguvgdrohhpvghn necukfhppeeliedrvdefledrudejrddvgedvnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomheptghonhhtrggtthestggrrhhlughonhhgrdhmvg X-ME-Proxy: Received: from [192.168.0.6] (pool-96-239-17-242.nycmny.fios.verizon.net [96.239.17.242]) by mail.messagingengine.com (Postfix) with ESMTPA id A659A24005A for <45165@debbugs.gnu.org>; Tue, 15 Dec 2020 19:45:03 -0500 (EST) From: Carl Dong Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: bug#45165: binutils-mesboot0 fails at configure, cannot find lex Date: Tue, 15 Dec 2020 19:46:16 -0500 References: <1C1332EB-3389-416F-A8A7-0CF6A469AE29@carldong.me> <3FFC3D46-B961-479D-BCA9-273C150BF9CC@carldong.me> <87a6ukkg1r.fsf@gnu.org> <58F8D6E0-B15D-47D2-A468-8620B9DBD90D@carldong.me> To: 45165@debbugs.gnu.org In-Reply-To: <58F8D6E0-B15D-47D2-A468-8620B9DBD90D@carldong.me> Message-Id: <1CB66010-F81E-447B-9715-B1A79415EAA6@carldong.me> X-Mailer: Apple Mail (2.3608.120.23.2.4) X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 45165 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Hi all, I think I have a new lead! Here=E2=80=99s what I did: 1. cd /tmp/guix-build-binutils-mesboot0-2.14.drv-0/binutils-2.14 2. env -i bash --rcfile environment-variables 3. Ran the configure command from the log, just to check: ./configure --disable-nls --disable-shared --disable-werror = --build=3Di386-unknown-linux --host=3Di386-unknown-linux = --target=3Di386-unknown-linux --with-sysroot=3D/ = --prefix=3D/gnu/store/jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2= .14 Indeed it did still output "not updating unwritable cache = ./config.cache=E2=80=9D However, when I tried `test -w config.cache`, there was no status = code=E2=80=A6 This led me to look at ./configure=E2=80=99s shebang, which is: = /gnu/store/m89p469fxwn4hj7an9givd1ry9vk7j2l-bash-mesboot0-2.05b/bin/sh Then I did: = /gnu/store/m89p469fxwn4hj7an9givd1ry9vk7j2l-bash-mesboot0-2.05b/bin/sh = -c "test -w config.cache=E2=80=9D Which _did_ exit with status=3D1 ! So I believe that this is a problem with the =E2=80=9Ctest=E2=80=9D = builtin in = /gnu/store/m89p469fxwn4hj7an9givd1ry9vk7j2l-bash-mesboot0-2.05b So I ran: env -i bash --rcfile environment-variables -c 'strace -v -e = trace=3Dfile /gnu/store/m89p469fxwn4hj7an9givd1ry = 9vk7j2l-bash-mesboot0-2.05b/bin/sh -c "test -w config.cache=E2=80=9D' And the output: = execve("/gnu/store/m89p469fxwn4hj7an9givd1ry9vk7j2l-bash-mesboot0-2.05b/bi= n/sh", ["/gnu/store/m89p469fxwn4hj7an9giv"..., "-c", "test -w = config.cache"], ["PWD=3D/tmp/guix-build-binutils-mes"..., "SHLVL=3D0", = "_=3D/usr/bin/strace"]) =3D 0 [ Process PID=3D2049037 runs in 32 bit mode. ] open("/dev/tty", O_RDWR) =3D 3 stat("/tmp/guix-build-binutils-mesboot0-2.14.drv-0", {st_dev=3Dmakedev(0, = 0x2f), st_ino=3D2546749, st_mode=3DS_IFDIR|0755, st_nlink=3D3, = st_uid=3D1000, st_gid=3D1000, st_blksize=3D4096, st_blocks=3D0, = st_size=3D80, st_atime=3D1608079054 /* = 2020-12-15T19:37:34.095396729-0500 */, st_atime_nsec=3D95396729, = st_mtime=3D1607635957 /* 2020-12-10T16:32:37.842047431-0500 */, = st_mtime_nsec=3D842047431, st_ctime=3D1607636165 /* = 2020-12-10T16:36:05.793930344-0500 */, st_ctime_nsec=3D793930344}) =3D 0 stat(".", {st_dev=3Dmakedev(0, 0x2f), st_ino=3D2546749, = st_mode=3DS_IFDIR|0755, st_nlink=3D3, st_uid=3D1000, st_gid=3D1000, = st_blksize=3D4096, st_blocks=3D0, st_size=3D80, st_atime=3D1608079054 /* = 2020-12-15T19:37:34.095396729-0500 */, st_atime_nsec=3D95396729, = st_mtime=3D1607635957 /* 2020-12-10T16:32:37.842047431-0500 */, = st_mtime_nsec=3D842047431, st_ctime=3D1607636165 /* = 2020-12-10T16:36:05.793930344-0500 */, st_ctime_nsec=3D793930344}) =3D 0 stat("config.cache", 0xfff9affc) =3D -1 ENOENT (No such file or = directory) +++ exited with 1 +++ I had a hunch that the mode is most likely the problem. So I tried the = following: chmod 664 config.cache -> status is still 1 chmod 646 config.cache -> status is now 0!! So somehow the =E2=80=9Ctest=E2=80=9D builtin for my bash-mesboot0 = doesn=E2=80=99t think that it has owner or group permissions to write to = a file that itself created? Let me know what you guys think could be the case! Cheers, Carl Dong=