adms: bootstrap phase fails

  • Done
  • quality assurance status badge
Details
2 participants
  • Christopher Howard
  • Z572
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

Christopher Howard wrote 2 months ago
(address . bug-guix@gnu.org)
87jzan29bv.fsf@librehacker.com
Hi, I am trying to build adms since it is a dependency of Qucs. But the build fails with this error:

```
starting phase `bootstrap'
running './bootstrap.sh'
In execvp of ./bootstrap.sh: Exec format error
error: in phase 'bootstrap': uncaught exception:
%exception #<&invoke-error program: "./bootstrap.sh" arguments: () exit-status: 127 term-signal: #f stop-signal: #f>
phase `bootstrap' failed after 0.0 seconds
command "./bootstrap.sh" failed with status 127
build process 6 exited with status 256
```

The command I used to build was "guix time-machine -- build adms". The build log is attached.
Attachment: 5ndp30zjzb6m8nysgiy76zfylw5v57-adms-2.3.7.drv.gz
Here is my system information:

```
christopher@theoden
-------------------
OS: Guix System x86_64
Host: OptiPlex 9020 00
Kernel: 6.11.8-gnu
Uptime: 6 days, 20 hours, 51 mins
Packages: 160 (guix-system)
Shell: bash 5.1.16
Resolution: 1920x1080
DE: GNOME
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: launch-local-em
CPU: Intel i5-4570 (4) @ 3.600GHz
GPU: AMD ATI Radeon HD 8490 / R5 235X OEM
GPU: Intel HD Graphics
Memory: 5740MiB / 15907MiB
```

--
馃摏 Christopher Howard
馃殌 gemini://gem.librehacker.com

讘专讗砖讬转 讘专讗 讗诇讛讬诐 讗转 讛砖诪讬诐 讜讗转 讛讗专抓
Z572 wrote 2 months ago
(name . Christopher Howard)(address . christopher@librehacker.com)(address . 75740-done@debbugs.gnu.org)
87ldv316zb.fsf@iscas.ac.cn
Christopher Howard <christopher@librehacker.com> writes:

Toggle quote (40 lines)
> Hi, I am trying to build adms since it is a dependency of Qucs. But the build fails with this error:
>
> ```
> starting phase `bootstrap'
> running './bootstrap.sh'
> In execvp of ./bootstrap.sh: Exec format error
> error: in phase 'bootstrap': uncaught exception:
> %exception #<&invoke-error program: "./bootstrap.sh" arguments: () exit-status: 127 term-signal: #f stop-signal: #f>
> phase `bootstrap' failed after 0.0 seconds
> command "./bootstrap.sh" failed with status 127
> build process 6 exited with status 256
> ```
>
> The command I used to build was "guix time-machine -- build adms". The build log is attached.
>
> [2. application/octet-stream; 5ndp30zjzb6m8nysgiy76zfylw5v57-adms-2.3.7.drv.gz]...
>
>
> Here is my system information:
>
> ```
> christopher@theoden
> -------------------
> OS: Guix System x86_64
> Host: OptiPlex 9020 00
> Kernel: 6.11.8-gnu
> Uptime: 6 days, 20 hours, 51 mins
> Packages: 160 (guix-system)
> Shell: bash 5.1.16
> Resolution: 1920x1080
> DE: GNOME
> Theme: Adwaita [GTK2/3]
> Icons: Adwaita [GTK2/3]
> Terminal: launch-local-em
> CPU: Intel i5-4570 (4) @ 3.600GHz
> GPU: AMD ATI Radeon HD 8490 / R5 235X OEM
> GPU: Intel HD Graphics
> Memory: 5740MiB / 15907MiB
> ```

Fixed, see
closing.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfr6klGDOXiwIdX/bO1qpk+Gi3/AFAmeQx2gACgkQO1qpk+Gi
3/DkVxAAuXs6NVsfOjlZHw9bfwmJH06NfxDdIxMOcISkIa5Z31P/97rIFTTKNl9m
VGSLePJTVbbfvMa+z42UiR+re1FFwJId/UJbqPyvqxoTiPDGDKIRfKcbDMXf2LGc
9+CkO9rNJN+6L5wLOvRHLuIKdaCOGvXLTPjvV/Y+U/1/DUromA0hFThjIX4Azj2c
TWkXVzzDH1hnUKjY+pLo+GmM86rgaAuja2MOXZbbAJxvHHRVts/Nmp5XEvnZkK5a
uBJSBBReD40VaCYUOysGb51qfm5XgS6zGmj/h+lbL67QI6WkrQFIr+QZ9q68HpVF
9luIBniAz7cctGvFQhFWHJ1Dc4fAd7PyiP6ZGTsV/+i9CULbe7Im7+iMPfxeXTmf
F/38rRfOWsNqZ8EZiVR8keqfzobS/U1nnRDyl0ry1vxJvz1umet6fUEzWZxlrT5P
eR4H82fMunlzD21qBada8HN68AGa7ICvjfLZfGqt72OBFNzj1MCO7RGqaDjofotY
nJ9b66KcxWf+t9ddMOYmyg9RANTLwPcsG35/MENWK5CdreMXrtY/lwWpDaA2IVEN
8WYqASUlqZ5G2M+x27IP3yuwGowqXWIB/EWpxt4NyW6OsJ+uWC7LNC+CyLclMI7z
49wfZRvgLy8RxN7elEt4gASXGp0xyTjeVYhqjZcx1jwKPRznj5c=
=7UkN
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 75740
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
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help