binutils-mesboot1-2.14 configure phase fails, In procedure stat: No such file or directory: "config.status"

  • Open
  • quality assurance status badge
Details
4 participants
  • Andreas Enge
  • Janneke Nieuwenhuizen
  • Ludovic Courtès
  • Christopher Baines
Owner
unassigned
Submitted by
Christopher Baines
Severity
normal
C
C
Christopher Baines wrote on 21 Jan 2022 18:00
(address . bug-guix@gnu.org)
87o845qanx.fsf@cbaines.net
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].


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
L
L
Ludovic Courtès wrote on 25 Jan 2022 23:42
(name . Christopher Baines)(address . mail@cbaines.net)(address . 53415@debbugs.gnu.org)
8735lbl9ok.fsf@gnu.org
Hi,

Christopher Baines <mail@cbaines.net> skribis:

Toggle quote (20 lines)
> 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:

Toggle snippet (4 lines)
$ uname -srv
Linux 5.15.12-gnu #1 SMP 1

This reminds me of:


Could it be something with the kernel options, as discussed at

Thanks,
Ludo’.
C
C
Christopher Baines wrote on 31 Jan 2022 20:38
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 53415@debbugs.gnu.org)
871r0nmznf.fsf@cbaines.net
Ludovic Courtès <ludo@gnu.org> writes:

Toggle quote (46 lines)
> Hi,
>
> Christopher Baines <mail@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)
Attachment: binutils-mesboot1-strace
-----BEGIN PGP SIGNATURE-----

iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmH4QwRfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF
ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh
aW5lcy5uZXQACgkQXiijOwuE9XdsDw/9HiNPG9h800Bsq+yh9Kof97yhhv5F/5Oa
ToUUewhtMyZkhW2veXkpK4el2FTh0pRj9L9Mz3M2BXifFpp02YTqNfL+fh+Rd3ML
xrZQ7TQdYQTvWbPPcKRIJUCY/pMclrGLr9vi7x7dBKQ+BQBsOnmhlRD8HJmPdq1d
4jw5jdkJzwEBwDlXy3pXFbCNGepaKADUD9REjNo7W8jwvfImjl00mKTPHeNseuM9
iA/+rMuQog0K0iTOkhdNhknznlbG7H359f9ZLYWS5/rxSWh5u9uyoba+yistmU1I
9zkJHAKt+WWq9YPfzd8z0PE+wUhTkQv3YTpAbuHPVg8sKMuHG4FsxJIsjRUTXJpu
PKIheKlRkdWUzRfjZ3Qb1quNlGp4LlUWYTuS8K1CPEr0mqSBKj+p8AbXg3Qj/6Bw
XDSGmLIpD2JBbLJF9NxdN0UN7Ah3UvjUzS20EJX4YQ9Kv1rDKH245LGlSesiQ3PZ
DCXMoAxcBgWQdoSy28fhV5uzOmXtJn8vfNLlBJjfPYWcLAR6qKm8BMkQHuiIUAOL
pW9/xAWvHXz4qrOpzwtsm7D5enqXbyjYFv3tobiKl2ZSU7Yeq0e8Ur273p5AYlKy
9jvYbmiCbZhp1XHY8eh7C21J4c99lbj93xEFfq5v32kM/BRY2NuRrK7mn+1vk4fe
JPqVgblA72c=
=tMwW
-----END PGP SIGNATURE-----

J
J
Janneke Nieuwenhuizen wrote on 16 Feb 2023 16:03
Re: Merging core-updates?
(name . Andreas Enge)(address . andreas@enge.fr)
87h6vlfya4.fsf@gnu.org
Andreas Enge writes:

Toggle quote (7 lines)
> 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@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com| Avatar® https://AvatarAcademy.com
A
A
Andreas Enge wrote on 16 Feb 2023 16:24
(name . Janneke Nieuwenhuizen)(address . janneke@gnu.org)
Y+5KklptkTuzW+dd@jurong
Am Thu, Feb 16, 2023 at 04:03:15PM +0100 schrieb Janneke Nieuwenhuizen:
Toggle quote (3 lines)
> 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
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53415@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53415
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch