cambalache.x86_64-linux fails configure

  • Done
  • quality assurance status badge
Details
2 participants
  • Greg Hogan
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal

Debbugs page

Maxim Cournoyer wrote 1 years ago
(name . bug-guix)(address . bug-guix@gnu.org)
87v88gsac7.fsf@gmail.com
Hello,

cuirass@gnu.org (Cuirass) writes:

Toggle quote (6 lines)
> <p>The build <b>cambalache.x86_64-linux</b> for specification <b>master</b> is broken. You
> can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/3101151/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/3101151/details

Toggle snippet (32 lines)
starting phase `configure'
The Meson build system
Version: 1.1.0
Source dir: /tmp/guix-build-cambalache-0.12.1.drv-0/source
Build dir: /tmp/guix-build-cambalache-0.12.1.drv-0/build
Build type: native build
Project name: cambalache
Project version: 0.12.1
C compiler for the host machine: gcc (gcc 11.3.0 "gcc (GCC) 11.3.0")
C linker for the host machine: gcc ld.bfd 2.38
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python3 found: YES (/gnu/store/91wasjkmy50p8fq0rf9jby80mnmq1fxr-python-3.10.7/bin/python3)
Message: Python module [1mlxml[0m >= 4.5.0 found: [32mYES[0m 4.9.1 None
Message: Python module [1mgi[0m >= 3.38.0 found: [32mYES[0m 3.42.2 None
Message: Python module [1mGLib[0m >= 2.66.0 found: [32mYES[0m 2.72.3 None
Message: Python module [1mGtk[0m >= 3.24.0 found: [32mYES[0m 3.24.37 3.0
Message: Python module [1mGtk[0m >= 4.0.0 found: [32mYES[0m 4.8.1 4.0
Message: Python module [1mWebKit2[0m >= 2.32.0 found: [31mNO[0m 4.1
Message: Python module [1mWebKit[0m >= 2.32.0 found: [32mYES[0m 2.42.3 6.0
Message: Python module [1mGtkSource[0m found: [32mYES[0m 4
Message: Python module [1mHandy[0m found: [32mYES[0m None
Message: Python module [1mAdw[0m found: [32mYES[0m 1.2.0 None

../source/meson.build:76:0: ERROR: Assert failed: One or more required modules where not found

A full log can be found at /tmp/guix-build-cambalache-0.12.1.drv-0/build/meson-logs/meson-log.txt
error: in phase 'configure': uncaught exception:
%exception #<&invoke-error program: "meson" arguments: ("setup" "--prefix=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1" "--buildtype=debugoptimized" "-Dc_link_args=-Wl,-rpath=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1/lib" "-Dcpp_link_args=-Wl,-rpath=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1/lib" "/tmp/guix-build-cambalache-0.12.1.drv-0/source") exit-status: 1 term-signal: #f stop-signal: #f>
phase `configure' failed after 2.8 seconds

--
Thanks,
Maxim
Greg Hogan wrote 2 weeks ago
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(address . 68130@debbugs.gnu.org)
CA+3U0Zk+6vVcxp-x+2grooDhtPW+0ydqcT9u616kCmSEaf5OCg@mail.gmail.com
On Fri, Dec 29, 2023 at 9:18 PM Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:
Toggle quote (48 lines)
>
> Hello,
>
> cuirass@gnu.org (Cuirass) writes:
>
> > <p>The build <b>cambalache.x86_64-linux</b> for specification <b>master</b> is broken. You
> > can find the detailed information about this build <a
> > href="https://ci.guix.gnu.org/build/3101151/details">here</a>.</p>
> >
> > https://ci.guix.gnu.org/build/3101151/details
>
> --8<---------------cut here---------------start------------->8---
> starting phase `configure'
> The Meson build system
> Version: 1.1.0
> Source dir: /tmp/guix-build-cambalache-0.12.1.drv-0/source
> Build dir: /tmp/guix-build-cambalache-0.12.1.drv-0/build
> Build type: native build
> Project name: cambalache
> Project version: 0.12.1
> C compiler for the host machine: gcc (gcc 11.3.0 "gcc (GCC) 11.3.0")
> C linker for the host machine: gcc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Program python3 found: YES (/gnu/store/91wasjkmy50p8fq0rf9jby80mnmq1fxr-python-3.10.7/bin/python3)
> Message: Python module [1mlxml[0m >= 4.5.0 found: [32mYES[0m 4.9.1 None
> Message: Python module [1mgi[0m >= 3.38.0 found: [32mYES[0m 3.42.2 None
> Message: Python module [1mGLib[0m >= 2.66.0 found: [32mYES[0m 2.72.3 None
> Message: Python module [1mGtk[0m >= 3.24.0 found: [32mYES[0m 3.24.37 3.0
> Message: Python module [1mGtk[0m >= 4.0.0 found: [32mYES[0m 4.8.1 4.0
> Message: Python module [1mWebKit2[0m >= 2.32.0 found: [31mNO[0m 4.1
> Message: Python module [1mWebKit[0m >= 2.32.0 found: [32mYES[0m 2.42.3 6.0
> Message: Python module [1mGtkSource[0m found: [32mYES[0m 4
> Message: Python module [1mHandy[0m found: [32mYES[0m None
> Message: Python module [1mAdw[0m found: [32mYES[0m 1.2.0 None
>
> ../source/meson.build:76:0: ERROR: Assert failed: One or more required modules where not found
>
> A full log can be found at /tmp/guix-build-cambalache-0.12.1.drv-0/build/meson-logs/meson-log.txt
> error: in phase 'configure': uncaught exception:
> %exception #<&invoke-error program: "meson" arguments: ("setup" "--prefix=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1" "--buildtype=debugoptimized" "-Dc_link_args=-Wl,-rpath=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1/lib" "-Dcpp_link_args=-Wl,-rpath=/gnu/store/ggvgc6lj6d1nc3yl78g6d314895183xc-cambalache-0.12.1/lib" "/tmp/guix-build-cambalache-0.12.1.drv-0/source") exit-status: 1 term-signal: #f stop-signal: #f>
> phase `configure' failed after 2.8 seconds
> --8<---------------cut here---------------end--------------->8---
>
> --
> Thanks,
> Maxim

Not sure who is responsible but after numerous consecutive failures
the cambalache.x86_64-linux build has now succeeded. Mark as done?

Finished
3 Mar 16:06 +0100

Weather
New success

Maxim Cournoyer wrote 2 weeks ago
(name . Greg Hogan)(address . code@greghogan.com)(address . 68130-done@debbugs.gnu.org)
87wmczwq42.fsf@gmail.com
Hi,

[...]

Toggle quote (3 lines)
> Not sure who is responsible but after numerous consecutive failures
> the cambalache.x86_64-linux build has now succeeded. Mark as done?

Done!

--
Thanks,
Maxim
Closed
?
Your comment

Commenting via the web interface is currently disabled.

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

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