GNU bug report logs - #53415
binutils-mesboot1-2.14 configure phase fails, In procedure stat: No such file or directory: "config.status"

Previous Next

To reply to this bug, email your comments to 53415 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: bug-guix <at> gnu.org
Subject: binutils-mesboot1-2.14 configure phase fails, In procedure stat: No
 such file or directory: "config.status"
Date: Fri, 21 Jan 2022 17:00:32 +0000

I've seen this failure consistently on one of the machines behind
bordeaux.guix.gnu.org, you can see the full logs via following the "View
build" links here [1].

1: http://data.guix.gnu.org/gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv

I've tried building multiple times on the machine where the failures
occurred, and it's not once succeeded.

From looking at the kept build directory, the config.status file doesn't
exist. There is config.status.VX1nZz, but it's empty.



starting phase `configure'
running ./configure --disable-nls --disable-shared --disable-werror --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu --with-sysroot=/ --prefix=/gnu/store/gvmha2v54svwzxigcbap8862rg3fya0w-binutils-mesboot1-2.14
error: in phase 'configure': uncaught exception:
system-error "stat" "~A: ~S" ("No such file or directory" "config.status") (2) 
phase `configure' failed after 0.0 seconds
Backtrace:
In ice-9/boot-9.scm:
 157: 16 [catch #t #<catch-closure c93c40> ...]
In unknown file:
   ?: 15 [apply-smob/1 #<catch-closure c93c40>]
In ice-9/boot-9.scm:
  63: 14 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 13 [eval # #]
In ice-9/boot-9.scm:
2320: 12 [save-module-excursion #<procedure cc1b00 at ice-9/boot-9.scm:3961:3 ()>]
3966: 11 [#<procedure cc1b00 at ice-9/boot-9.scm:3961:3 ()>]
1645: 10 [%start-stack load-stack #<procedure cc2ba0 at ice-9/boot-9.scm:3957:10 ()>]
1650: 9 [#<procedure cc8db0 ()>]
In unknown file:
   ?: 8 [primitive-load "/gnu/store/6i3748r9if4cnjz1bmzh2ghbp0zlv232-binutils-mesboot1-2.14-builder"]
In ice-9/boot-9.scm:
 157: 7 [catch srfi-34 ...]
In srfi/srfi-1.scm:
 616: 6 [for-each #<procedure 11a5f60 at guix/build/gnu-build-system.scm:911:14 (expr)> ...]
In ice-9/boot-9.scm:
 171: 5 [with-throw-handler #t ...]
In guix/build/gnu-build-system.scm:
 927: 4 [#<procedure 177ce00 at guix/build/gnu-build-system.scm:926:21 ()>]
In ice-9/eval.scm:
 432: 3 [eval # #]
In guix/build/utils.scm:
 844: 2 [with-atomic-file-replacement "config.status" ...]
In unknown file:
   ?: 1 [stat "config.status" #<undefined>]
In ice-9/boot-9.scm:
 106: 0 [#<procedure 177cdc0 at ice-9/boot-9.scm:97:6 (thrown-k . args)> system-error ...]

ice-9/boot-9.scm:106:20: In procedure #<procedure 177cdc0 at ice-9/boot-9.scm:97:6 (thrown-k . args)>:
ice-9/boot-9.scm:106:20: In procedure stat: No such file or directory: "config.status"
builder for `/gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv' failed with exit code 1

Message #8 received at 53415 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 53415 <at> debbugs.gnu.org
Subject: Re: bug#53415: binutils-mesboot1-2.14 configure phase fails, In
 procedure stat: No such file or directory: "config.status"
Date: Tue, 25 Jan 2022 23:42:03 +0100

Hi,

Christopher Baines <mail <at> cbaines.net> skribis:

> I've seen this failure consistently on one of the machines behind
> bordeaux.guix.gnu.org, you can see the full logs via following the "View
> build" links here [1].
>
> 1: http://data.guix.gnu.org/gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv
>
> I've tried building multiple times on the machine where the failures
> occurred, and it's not once succeeded.
>
>>From looking at the kept build directory, the config.status file doesn't
> exist. There is config.status.VX1nZz, but it's empty.
>
>
>
> starting phase `configure'
> running ./configure --disable-nls --disable-shared --disable-werror --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu --with-sysroot=/ --prefix=/gnu/store/gvmha2v54svwzxigcbap8862rg3fya0w-binutils-mesboot1-2.14
> error: in phase 'configure': uncaught exception:
> system-error "stat" "~A: ~S" ("No such file or directory" "config.status") (2) 
> phase `configure' failed after 0.0 seconds

I just tried this on my laptop:

  guix build \
    /gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv \
    --check

and the ‘configure’ phase completes without problems.  I have:

--8<---------------cut here---------------start------------->8---
$ uname -srv
Linux 5.15.12-gnu #1 SMP 1
--8<---------------cut here---------------end--------------->8---

This reminds me of:

  https://issues.guix.gnu.org/49985
  https://issues.guix.gnu.org/45165

Could it be something with the kernel options, as discussed at
<https://issues.guix.gnu.org/45165#16>?

Thanks,
Ludo’.

Message #11 received at 53415 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 53415 <at> debbugs.gnu.org
Subject: Re: bug#53415: binutils-mesboot1-2.14 configure phase fails, In
 procedure stat: No such file or directory: "config.status"
Date: Mon, 31 Jan 2022 19:38:14 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi,
>
> Christopher Baines <mail <at> cbaines.net> skribis:
>
>> I've seen this failure consistently on one of the machines behind
>> bordeaux.guix.gnu.org, you can see the full logs via following the "View
>> build" links here [1].
>>
>> 1: http://data.guix.gnu.org/gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv
>>
>> I've tried building multiple times on the machine where the failures
>> occurred, and it's not once succeeded.
>>
>>>From looking at the kept build directory, the config.status file doesn't
>> exist. There is config.status.VX1nZz, but it's empty.
>>
>>
>>
>> starting phase `configure'
>> running ./configure --disable-nls --disable-shared --disable-werror
>> --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu
>> --with-sysroot=/
>> --prefix=/gnu/store/gvmha2v54svwzxigcbap8862rg3fya0w-binutils-mesboot1-2.14
>> error: in phase 'configure': uncaught exception:
>> system-error "stat" "~A: ~S" ("No such file or directory" "config.status") (2) 
>> phase `configure' failed after 0.0 seconds
>
> I just tried this on my laptop:
>
>   guix build \
>     /gnu/store/xd8rnmr0k3fhfhilzi66hnggsnx67d5i-binutils-mesboot1-2.14.drv \
>     --check
>
> and the ‘configure’ phase completes without problems.  I have:
>
> $ uname -srv
> Linux 5.15.12-gnu #1 SMP 1
>
> This reminds me of:
>
>   https://issues.guix.gnu.org/49985
>   https://issues.guix.gnu.org/45165
>
> Could it be something with the kernel options, as discussed at
> <https://issues.guix.gnu.org/45165#16>?

I was on the following Linux from Guix revision
fe58f05b2482fd45c41fe324ac0d393093dc163e:

Linux 5.15.13-gnu #1 SMP 1

I've tried reconfiguring with f8633a739511e8d5bef93b18b346efb69b91ac8e
which provides Linux 5.15.12, but I see the same behaviour.

Looking at the successful build log, I've realised that the ./configure
script is probably crashing, not producing the config.status file, which
is causing the exception seen.

I've tried stracing everything, and attached the portion from around
where ./configure starts, to the Guile exception for the end of the
build.

I did notice some suspicious looking bits like the following:

stat("/tmp/guix-build-binutils-mesboot1-2.14.drv-0", 0xffffd058) = -1 EOVERFLOW (Value too large for defined data type)

[binutils-mesboot1-strace (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 53415 <at> debbugs.gnu.org (full text, mbox):

From: Janneke Nieuwenhuizen <janneke <at> gnu.org>
To: Andreas Enge <andreas <at> enge.fr>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 49985 <at> debbugs.gnu.org,
 41264 <at> debbugs.gnu.org, 53416 <at> debbugs.gnu.org, guix-devel <at> gnu.org,
 53415 <at> debbugs.gnu.org
Subject: Re: Merging core-updates?
Date: Thu, 16 Feb 2023 16:03:15 +0100

Andreas Enge writes:

> Am Wed, Feb 15, 2023 at 09:39:39AM +0100 schrieb Janneke Nieuwenhuizen:
>> I have released 0.24.2 and updated mes-boot on core-updates as
>> Let's hope this fixes these bugs.
>
> With your latest patch, I have successfully bootstrapped core-updates
> on x86_64 up to hello and mpc. Thanks a lot!

Great, thanks so much for checking!  Are you using any of tmpfs or btrfs
on /tmp?

Greetings,
janneke

-- 
Janneke Nieuwenhuizen <janneke <at> gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com

Message #17 received at 53415 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Janneke Nieuwenhuizen <janneke <at> gnu.org>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 49985 <at> debbugs.gnu.org,
 41264 <at> debbugs.gnu.org, 53416 <at> debbugs.gnu.org, guix-devel <at> gnu.org,
 53415 <at> debbugs.gnu.org
Subject: Re: Merging core-updates?
Date: Thu, 16 Feb 2023 16:24:02 +0100

Am Thu, Feb 16, 2023 at 04:03:15PM +0100 schrieb Janneke Nieuwenhuizen:
> Great, thanks so much for checking!  Are you using any of tmpfs or btrfs
> on /tmp?

No, it is all on SSD, so we probably cannot conclude for the bugs,
unfortunately.

Andreas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.