bootstrap phase attempts to run a directory

  • Open
  • quality assurance status badge
Details
4 participants
  • Gábor Boskovits
  • Julien Lepiller
  • Ludovic Courtès
  • Christopher Baines
Owner
unassigned
Submitted by
Christopher Baines
Severity
normal
C
C
Christopher Baines wrote on 12 Jun 2018 00:50
(address . bug-guix@gnu.org)
87h8m9rl9b.fsf@cbaines.net
I've just noticed that the erlang package has started failing to
build. It looks like the bootstrap phase is over eager, and attempts to
run the bootstrap directory.

I think I'll fix this by deleting the phase, when I get around to
merging the changes in #31678, but this might be affecting other
packages, or possible to sure up so it doesn't break under this
circumstance.


starting phase `bootstrap'
running './bootstrap'
Backtrace:
8 (primitive-load "/gnu/store/g1n7gbvcqcaj9s41gk62x7crc34?")
In ice-9/eval.scm:
191:35 7 (_ _)
In srfi/srfi-1.scm:
640:9 6 (for-each #<procedure 80ea00 at /gnu/store/f95ghy8mx00?> ?)
In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/gnu-build-system.scm:
799:31 5 (_ _)
196:20 4 (bootstrap #:bootstrap-scripts _)
In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/utils.scm:
178:8 3 (call-with-ascii-input-file _ _)
831:24 2 (_ #<input: ./bootstrap 14>)
792:2 1 (get-char* _)
In unknown file:
0 (get-u8 #<input: ./bootstrap 14>)

ERROR: In procedure get-u8:
In procedure fport_read: Is a directory
builder for `/gnu/store/v5dshhj3bka541h12fk2xskmfj38y8qs-erlang-20.2.3.drv' failed with exit code 1
@ build-failed /gnu/store/v5dshhj3bka541h12fk2xskmfj38y8qs-erlang-20.2.3.drv - 1 builder for `/gnu/store/v5dshhj3bka541h12fk2xskmfj38y8qs-erlang-20.2.3.drv' failed with exit code 1
guix build: error: build failed: build of `/gnu/store/v5dshhj3bka541h12fk2xskmfj38y8qs-erlang-20.2.3.drv' failed
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAlse/KBfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF
ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE
9XcfYA/+OaugNlYFZcPjaonel7wivx/84y1vW/PIC8FPmIXtv4V5yl7tUzIBjh7Y
IY/UEQFAejFGZm1bsNZPkoOlK6xXuAem1Sat65BufUhHiDvO5gmTt0FON5kIBUwh
lpU4f1Xa9CFg9eWj/FY3y6HFKt+ppnqjiS/vYTa+9CCNyC9JO8fH3pvgqnujs9IZ
I5uaydW4fEsIMZQrQrVJosb8jtpZZF0NjHJtPkKkd/Mv2XWcCXeYxsvL6Xh7VRfL
Mde6tRAgejdCQ9HBszD0ghPwD3Ly8AuyzW8eo/SGrxavvPvruKO0wEcgDxBn33R1
kygau/bCbm3nxVfdxJjCNdH5ExOuOloRWCoJ03/JPQpf/d7cgW+GD5pPqjmBhA8j
DrJ3gAFXi9E7Ak+DCp1AX8CIDqjDuGL+nug0z9865mW5U6AavuLcHfktvKIXOTuE
sMnfdn4V1OhlpL1Oy2M/p+GkWbTS1Bzq1M2TMpdkLncF7y/h7SOWA0mmitQR0uQf
wHYLxBTqPBGQdArLvPo2/sQI/iOOfkBojoTWfpxCxRvJpvrah+b+ZdIYw+78d5M6
IZEZyG72nJ4jdz0IARoqFkrI2JHIcrje+rJt7B332uOH0ugYiT21veZ907p95A9s
Vj0NBiOzT+sx7WuArmoszEu/0fpdzoIU1Cza05ftPFMQ8Uxfz30=
=CNXV
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 12 Jun 2018 15:59
(name . Christopher Baines)(address . mail@cbaines.net)(address . 31791@debbugs.gnu.org)
874li8p0kl.fsf@gnu.org
Christopher Baines <mail@cbaines.net> skribis:

Toggle quote (6 lines)
> I've just noticed that the erlang package has started failing to
> build. It looks like the bootstrap phase is over eager, and attempts to
> run the bootstrap directory.
>
> I think I'll fix this by deleting the phase,

That’s probably the right thing to do. The new ‘bootstrap’ phase
introduced in core-updates would run anything called ‘bootstrap’, but it
doesn’t check whether that thing is a directory…

Ludo’.
G
G
Gábor Boskovits wrote on 12 Jun 2018 16:48
(name . Ludovic Courtès)(address . ludo@gnu.org)
CAE4v=pg9sS7-tOy9tAVRGamnpr_gnNFr34ZRyDADnfiyarw87w@mail.gmail.com
2018-06-12 15:59 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:

Toggle quote (13 lines)
> Christopher Baines <mail@cbaines.net> skribis:
>
> > I've just noticed that the erlang package has started failing to
> > build. It looks like the bootstrap phase is over eager, and attempts to
> > run the bootstrap directory.
> >
> > I think I'll fix this by deleting the phase,
>
> That’s probably the right thing to do. The new ‘bootstrap’ phase
> introduced in core-updates would run anything called ‘bootstrap’, but it
> doesn’t check whether that thing is a directory…
>
>
If this is a single occurrence, then I agree this is the way to go, but I
would
make a mental note to fix this in the phase, if this turn out to be more
widespread.


Toggle quote (5 lines)
> Ludo’.
>
>
>
>
Attachment: file
J
J
Julien Lepiller wrote on 13 Jun 2018 11:29
(address . 31791@debbugs.gnu.org)
8734d1dcc7dd2ad3bdf62b2f62d4adb9@lepiller.eu
Le 2018-06-12 15:59, ludo@gnu.org a écrit :
Toggle quote (16 lines)
> Christopher Baines <mail@cbaines.net> skribis:
>
>> I've just noticed that the erlang package has started failing to
>> build. It looks like the bootstrap phase is over eager, and attempts
>> to
>> run the bootstrap directory.
>>
>> I think I'll fix this by deleting the phase,
>
> That’s probably the right thing to do. The new ‘bootstrap’ phase
> introduced in core-updates would run anything called ‘bootstrap’, but
> it
> doesn’t check whether that thing is a directory…
>
> Ludo’.

ocaml-build also has this issue.
J
J
Julien Lepiller wrote on 13 Jun 2018 12:02
(address . 31791@debbugs.gnu.org)
ca1dce1c6b9a150f569eb77bf1ae2d74@lepiller.eu
Le 2018-06-13 11:29, Julien Lepiller a écrit :
Toggle quote (19 lines)
> Le 2018-06-12 15:59, ludo@gnu.org a écrit :
>> Christopher Baines <mail@cbaines.net> skribis:
>>
>>> I've just noticed that the erlang package has started failing to
>>> build. It looks like the bootstrap phase is over eager, and attempts
>>> to
>>> run the bootstrap directory.
>>>
>>> I think I'll fix this by deleting the phase,
>>
>> That’s probably the right thing to do. The new ‘bootstrap’ phase
>> introduced in core-updates would run anything called ‘bootstrap’, but
>> it
>> doesn’t check whether that thing is a directory…
>>
>> Ludo’.
>
> ocaml-build also has this issue.

Nevermind, it's not (yet) part of guix :)
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 31791
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