ocamlc -a -o findlib.cma findlib_config.cmo fl_split.cmo fl_metatoken.cmo fl_meta.cmo fl_metascanner.cmo fl_topo.cmo fl_package_base.cmo findlib.cmo ocamlc -a -o findlib_top.cma topfind.cmo ocamlc -custom -o ocamlfind findlib.cma unix.cma \ ocaml_args.cmo frontend.cmo make[1]: Leaving directory `/var/tmp/portage/dev-ml/findlib-1.2.4/work/findlib-1.2.4/src/findlib' make[1]: Entering directory `/var/tmp/portage/dev-ml/findlib-1.2.4/work/findlib-1.2.4/src/findlib-toolbox' ocamlc -o make_wizard -I +labltk -I ../findlib unix.cma str.cma labltk.cma \ findlib.cma make_wizard.ml File "make_wizard.ml", line 1288, characters 6-12: Warning Y: unused variable update. Error on dynamically loaded library: /usr/lib64/ocaml/stublibs/dlllabltk.so: libtk8.4.so: cannot open shared object file: No such file or directory make[1]: *** [make_wizard] Error 2 make[1]: Leaving directory `/var/tmp/portage/dev-ml/findlib-1.2.4/work/findlib-1.2.4/src/findlib-toolbox' make: *** [all] Error 2 * * ERROR: dev-ml/findlib-1.2.4 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 879: Called die * The specific snippet of code: * emake all || die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-ml/findlib-1.2.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-ml/findlib-1.2.4/temp/environment'. * Reproducible: Always
Created attachment 194139 [details] Environment
Created attachment 194141 [details] Build Log
Just a guess: is it possible, that you've recently upgraded from tcl/tk 8.4 to 8.5 ? If so, you may require revdep-rebuild.
From your build.log: Error on dynamically loaded library: /usr/lib64/ocaml/stublibs/dlllabltk.so: libtk8.4.so: cannot open shared object file: No such file or directory I agree with Rafał. Please run revdep-rebuild (from app-portage/gentoolkit package) and reopen this bug if that didn't fix your problem. Don't forget to post your "emerge --info" as well when you reopen the bug.
