Bug 941618 – dev-ml/opam-2.1.6 - [libtool] make inconsistent assumptions over implementation Cudf

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2024-10-16 08:47:16 UTC]

too long lines were shrinked:

    ocamlopt src/client/opam_client.{a,cmxa}
    ocamlopt src/client/opamMain.exe (exit 2)
(cd _build/default && /usr/bin/ocamlopt.opt -w -40 -warn-error -3-9-33 -w +a-4-40-42-44-48 -safe-string -w -67 -g -o src/client/opamMain.exe /usr/lib64/ocaml/re/re.cmxa /usr/lib64/ocaml/stdlib-shims/stdlib_shims.cmxa /usr/lib64/ocaml/ocamlgraph/graph.cmxa /usr/lib64/ocaml/unix.cmxa -I /usr/lib64/oca
File "_none_", line 1:
Error: Files /usr/lib64/ocaml/mccs/mccs.cmxa
       and /usr/lib64/ocaml/cudf/cudf.cmxa
       make inconsistent assumptions over implementation Cudf
    ocamlopt src/client/opam_client.cmxs          
 * ERROR: dev-ml/opam-2.1.6::gentoo failed (compile phase):

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 23.0_desktop-20241011-134002

  UNMASKED:
  <sys-devel/gcc-15.0.9999:15

  The attached etc.portage.tar.xz has all details.
  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-15 *
clang version 19.1.1
llvm-config: 19.1.1
Python 3.12.7
go version go1.23.1 linux/amd64
  (none found)
Available Rust versions:
  [1]   rust-bin-1.81.0 *
The following VMs are available for generation-2:
1)	Eclipse Temurin JDK 17.0.12_p7 [openjdk-bin-17]
2)	Eclipse Temurin JDK 21.0.4_p7 [openjdk-bin-21]
*)	Eclipse Temurin JDK 8.422_p05 [openjdk-bin-8]
Available Java Virtual Machines:
  [1]   openjdk-bin-8  system-vm
  [2]   openjdk-bin-17 
  [3]   openjdk-bin-21 

The Glorious Glasgow Haskell Compilation System, version 9.2.8

  HEAD of ::gentoo
commit 58c9d99995b0de78f962c17f7dee003260f17d98
Author: Repository mirror & CI <[e-mail]>
Date:   Wed Oct 16 06:48:47 2024 +0000

    2024-10-16 06:48:47 UTC

emerge -qpvO =dev-ml/opam-2.1.6

[Comment 1 Toralf Förster 2024-10-16 08:47:17 UTC]

Created attachment 906054 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2024-10-16 08:47:18 UTC]

Created attachment 906055 [details]
dev-ml:opam-2.1.6:20241016-074810.log

[Comment 3 Toralf Förster 2024-10-16 08:47:20 UTC]

Created attachment 906056 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2024-10-16 08:47:21 UTC]

Created attachment 906057 [details]
environment

[Comment 5 Toralf Förster 2024-10-16 08:47:21 UTC]

Created attachment 906058 [details]
etc.clang.tar.xz

[Comment 6 Toralf Förster 2024-10-16 08:47:22 UTC]

Created attachment 906059 [details]
etc.portage.tar.xz

[Comment 7 Toralf Förster 2024-10-16 08:47:23 UTC]

Created attachment 906060 [details]
logs.tar.xz

[Comment 8 Toralf Förster 2024-10-16 08:47:24 UTC]

Created attachment 906061 [details]
qlist-info.txt.xz

[Comment 9 Toralf Förster 2024-10-16 08:47:25 UTC]

Created attachment 906062 [details]
temp.tar.xz

[Comment 10 Andrei Slavoiu 2024-10-16 10:51:05 UTC]

Not related to gcc-15, I got this on my desktop that is a regular ~x86_64 with no unmasked packages or extra repositories.

[Comment 11 Andrei Slavoiu 2024-10-16 10:51:34 UTC]

Created attachment 906072 [details]
emerge --info

[Comment 12 Andrei Slavoiu 2024-10-16 10:51:59 UTC]

Created attachment 906073 [details]
build.log

[Comment 13 Tupone Alfredo 2024-10-16 17:34:53 UTC]

what happen if you emerge -C all the dev-ml packages and the emerge opam ?

To me the sequence of build in emerge-history.txt seems good

[Comment 14 Andrei Slavoiu 2024-10-17 09:41:30 UTC]

(In reply to Tupone Alfredo from comment #13)
> what happen if you emerge -C all the dev-ml packages and the emerge opam ?
> 
> To me the sequence of build in emerge-history.txt seems good

I can try that. So far, after the sync today, I also hit Bug 941641

[Comment 15 Andrei Slavoiu 2024-10-17 09:51:33 UTC]

After removing all dev-ml packages, this one builds without issues.