Please stabilize
amd64 done
x86 done
arm64 done
arm done
Created attachment 911975 [details] output of emerge --info '=dev-ml/lwt-5.7.0::gentoo'
Created attachment 911976 [details] output of emerge -pvq libguestfs
Created attachment 911977 [details] output of emerge -pqv libguestfs
when emerging libguestfs, dev-ml/lwt-5.7.0 gets pulled in as a dependency and fails to build * Messages for package dev-ml/lwt-5.7.0: * ERROR: dev-ml/lwt-5.7.0::gentoo failed (compile phase): * Failed to run command: dune build @install --display=short --profile release -j 16 --for-release-of-packages=lwt,lwt_ppx,lwt_ppx_let,lwt_react * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 638: Called dune-compile 'lwt' 'lwt_ppx' 'lwt_ppx_let' 'lwt_react' * environment, line 315: Called dune-release 'build' '--target' '@install' 'lwt' 'lwt_ppx' 'lwt_ppx_let' 'lwt_react' * environment, line 356: Called edune 'build' '@install' '--display=short' '--profile' 'release' '-j' '16' '--for-release-of-packages=lwt,lwt_ppx,lwt_ppx_let,lwt_react' * environment, line 553: Called edo 'dune' 'build' '@install' '--display=short' '--profile' 'release' '-j' '16' '--for-release-of-packages=lwt,lwt_ppx,lwt_ppx_let,lwt_react' * environment, line 514: Called die * The specific snippet of code: * "$@" || die -n "Failed to run command: $@" * * If you need support, post the output of `emerge --info '=dev-ml/lwt-5.7.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-ml/lwt-5.7.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-ml/lwt-5.7.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ml/lwt-5.7.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-ml/lwt-5.7.0/work/lwt-5.7.0' * S: '/var/tmp/portage/dev-ml/lwt-5.7.0/work/lwt-5.7.0'
(In reply to f16poom@gmail.com from comment #8) > when emerging libguestfs, dev-ml/lwt-5.7.0 gets pulled in as a dependency > and fails to build Please upload the log file of failed package.
Created attachment 911979 [details] dev-ml/lwt-5.7.0 build log
(In reply to f16poom@gmail.com from comment #10) > Created attachment 911979 [details] > dev-ml/lwt-5.7.0 build log does "emerge -1v dev-ml/ppxlib && emerge -1v dev-ml/lwt" solve it?
Created attachment 911982 [details] build log after trying emerge -1v dev-ml/ppxlib && emerge -1v dev-ml/lwt ppxlib builds, lwt doesn't
(In reply to f16poom@gmail.com from comment #12) > Created attachment 911982 [details] > build log after trying emerge -1v dev-ml/ppxlib && emerge -1v dev-ml/lwt > > ppxlib builds, lwt doesn't In 1st lwt log we see: Files /usr/lib64/ocaml/ppxlib/astlib/astlib.cmxa and /usr/lib64/ocaml/compiler-libs/ocamlcommon.cmxa make inconsistent assumptions over implementation Location This is caused by wrong build order of ppxlib. We can see that ppxlib is to blame because "qfile /usr/lib64/ocaml/ppxlib/astlib/astlib.cmxa" gives "dev-ml/ppxlib". Are there now any other "Files X and Y make inconsistent assumptions" on the new build failure? BTW: lwt 5.7.0 rebuilds fine for me.
Sorry, I don't understand. Should I perhaps clean and rebuild everything?
(In reply to f16poom@gmail.com from comment #14) > Sorry, I don't understand. Should I perhaps clean and rebuild everything? You can try it. This lock behavior sometimes happens in OCaml ecosystem. You cna either: a) grep the build logs for "make inconsistent assumptions" b) force-uninstall all dev-ml packages and re-emerge them
I clean and tried re-emerging, exact same build.log error. sudo grep "make inconsistent assumptions" /var/tmp/portage/dev-ml/lwt-5.7.0/temp/build.log make inconsistent assumptions over implementation Location what other logs should I grep?
(In reply to f16poom@gmail.com from comment #16) > I clean and tried re-emerging, exact same build.log error. > > sudo grep "make inconsistent assumptions" > /var/tmp/portage/dev-ml/lwt-5.7.0/temp/build.log > make inconsistent assumptions over implementation Location > > what other logs should I grep? well, you also have to look above that message cause only form that line you do not know what files are to blame
Created attachment 911983 [details] output near make inconsistent assumptions over implementation Location
(In reply to f16poom@gmail.com from comment #18) > Created attachment 911983 [details] > output near make inconsistent assumptions over implementation Location I see it still fails on the same file from ppxlib (/usr/lib64/ocaml/ppxlib/astlib/astlib.cmxa).
f16poom, any luck with latest unstable lwt + luv?
Created attachment 911984 [details] output after trying unstable lwt & luv
Created attachment 911985 [details] my make.conf Hopefully it's just a case of me missing something idiotic. I use binpkgs
(In reply to f16poom@gmail.com from comment #21) > Created attachment 911984 [details] > output after trying unstable lwt & luv Upload the full log file in this case, please.
(In reply to f16poom@gmail.com from comment #22) > Created attachment 911985 [details] > my make.conf > > Hopefully it's just a case of me missing something idiotic. I use binpkgs Have you re-emerged ppxlib as binary?
Created attachment 911989 [details] unstable lwt & luv ppxlib had always been emerged as a binary
(In reply to f16poom@gmail.com from comment #25) > Created attachment 911989 [details] > unstable lwt & luv > > ppxlib had always been emerged as a binary Well, that's wrong, try again ... as non-binary :) Because the OCaml bytecode will be exactly the same with a binary - so here you were just running in a circle.
(In reply to f16poom@gmail.com from comment #25) > Created attachment 911989 [details] > unstable lwt & luv > > ppxlib had always been emerged as a binary Did you emerge with --deep ? --deep is almost mandatory for ocaml packages
I feel so stupid hahaha! sudo FEATURES="-getbinpkg" emerge -1vq --deep dev-ml/ppxlib && sudo emerge -1vq dev-ml/lwt >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Installing (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Completed (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Jobs: 1 of 1 complete Load avg: 0.43, 0.20, 0.13 >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-ml/lwt-5.9.0::gentoo >>> Installing (1 of 1) dev-ml/lwt-5.9.0::gentoo >>> Completed (1 of 1) dev-ml/lwt-5.9.0::gentoo >>> Jobs: 1 of 1 complete Load avg: 1.55, 0.47, 0.22 Now that unstable works, I'll remove ~amd and try to emerge the stable 5.7 version.
sudo FEATURES="-getbinpkg" emerge -1vq --deep dev-ml/ppxlib && sudo emerge -1vq dev-ml/lwt >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Installing (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Completed (1 of 1) dev-ml/ppxlib-0.30.0-r2::gentoo >>> Jobs: 1 of 1 complete Load avg: 1.36, 0.65, 0.33 >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-ml/lwt-5.7.0::gentoo >>> Installing (1 of 1) dev-ml/lwt-5.7.0::gentoo >>> Completed (1 of 1) dev-ml/lwt-5.7.0::gentoo >>> Jobs: 1 of 1 complete Load avg: 2.22, 0.89, 0.42 Stable lwt & luv works. I guess this will just be a gotcha for people building libguestfs while using getbinpkg since ppxlib gets called in as a binary. Thank you so much for taking the time to help me.
ppc64 done all arches done
