tommy3001

...there is is a missing information, sorry.... this ebuild was copied from the gentoo repository. The reason was, that I got the message during the installation of opencascade that i need the following version of libharu as dependancy, but it is not included in the funtoo repo: media-libs/libharu-2.3.0-r2

libharu is a requirement of freecad... The Output from emerge libharu is: * ERROR: media-libs/libharu-2.3.0-r2::media-kit failed (prepare phase): * patch -p1 failed with /var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-1-Included-necessary-char-widths-in-generated-PDF.patch * * Call stack: * ebuild.sh, line 92: Called src_prepare * environment, line 3662: Called cmake-utils_src_prepare * environment, line 870: Called _cmake_execute_optionally 'src_prepare' * environment, line 306: Called enable_cmake-utils_src_prepare * environment, line 1340: Called default_src_prepare * phase-functions.sh, line 932: Called __eapi6_src_prepare * environment, line 237: Called eapply '/var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-1-Included-necessary-char-widths-in-generated-PDF.patch' '/var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-2-Avoid-issue-with-libtiff-duplicate-symbols.patch' '/var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-3-cmake-fixes.patch' '/var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-4-Add-support-for-free-form-triangle-Shading-objects.patch' * environment, line 1052: Called _eapply_patch '/var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-1-Included-necessary-char-widths-in-generated-PDF.patch' * environment, line 990: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/media-libs/libharu-2.3.0-r2/files/libharu-2.3.0-1-Included-necessary-char-widths-in-generated-PDF.patch' * isolated-functions.sh, line 121: Called die * The specific snippet of code: * die "$@" emerge_info_libharu.txt

>>> Failed to emerge media-libs/mesa-18.2.0_rc2, Log file: >>> '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/temp/build.log' * Messages for package media-libs/mesa-18.2.0_rc2: * ERROR: media-libs/mesa-18.2.0_rc2::xorg-kit failed (compile phase): * ninja -v -j6 -l0 -C /var/tmp/portage/media-libs/mesa-18.2.0_rc2/work/mesa-18.2.0-rc2-abi_x86_32.x86 failed * * Call stack: * ebuild.sh, line 92: Called src_compile * environment, line 3394: Called multilib-minimal_src_compile * environment, line 1932: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' * environment, line 2163: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1798: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 1796: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' * environment, line 830: Called multilib-minimal_abi_src_compile * environment, line 1926: Called multilib_src_compile * environment, line 2375: Called meson_src_compile * environment, line 1720: Called eninja '-C' '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/work/mesa-18.2.0-rc2-abi_x86_32.x86' * environment, line 1245: Called die * The specific snippet of code: * "$@" || die "${nonfatal_args[@]}" "${*} failed" * * If you need support, post the output of `emerge --info '=media-libs/mesa-18.2.0_rc2::xorg-kit'`, * the complete build log and the output of `emerge -pqv '=media-libs/mesa-18.2.0_rc2::xorg-kit'`. * The complete build log is located at '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/temp/environment'. * Working directory: '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/work/mesa-18.2.0-rc2-abi_x86_32.x86' * S: '/var/tmp/portage/media-libs/mesa-18.2.0_rc2/work/mesa-18.2.0-rc2' Remove of the use flag xa did not solve my issue, too....

I have a similar Problem.... (original nvidia driver )

I ran in trouble during my last emerge -auDN @world The error message I got during the compilation of mesa-18.2.0_rc2 is Meson encountered an error in file meson.build, line 593, column 4: Problem encountered: XA state tracker requires at least one of the following gallium drivers: nouveau, freedreno, i915, svga. That is the first time that I see this error message. Everything works fine regarding mesa until now.... I have a good working nvidia card and regarding original nvidia driver installed. At the moment there is now known reason to use gallium from my view. emerge_info_mesa.txt

Oh Yes. You are right. The rebuild with emerge -auDN --newuse @world added the GdkPixbuf-2.0.gir file in the folder.... Thanks for support. I learned a lot about funtoo the last few days. ;-)

Ok. It is obvious that GdkPixbuf-2.0.gir is not present in the specified folder /usr/share/gir-1.0/. I can just download it from another repository, like https://github.com/gtk-rs/gir-files but I think that is not the normal way to handle such an issues... Is there an additional necessary package available?

Thanks for your support. Yes, gobject-introspection is installed. In the attachment you can find the output of "equery f gobject-introspection" query_gobject_introspection.txt

Ok, thanks. But now I got a new issue during the installation of the dependancy appstream: In the attachment you can find the output of emerge --info appstream and the build log. emerge_info_appstream build_log_appstream

Hallo. I got an error during the installation of gimp with emerge -atv gimp. Output: - media-libs/gexiv2-0.10.6::media-kit USE="python -introspection -static-libs -test" PYTHON_TARGETS="python2_7 python3_4 -python3_5" The following REQUIRED_USE flag constraints are unsatisfied: python? ( introspection ) The above constraints are a subset of the following complete expression: python? ( introspection any-of ( python_targets_python2_7 python_targets_python3_4 python_targets_python3_5 ) ) test? ( python ) (dependency required by "media-gfx/gimp-2.9.6::media-kit" [ebuild]) (dependency required by "gimp" [argument]) In the attachment is the output of emerge --info '=media-libs/gexiv2-0.10.6' emerge_info_gimp.txt

Hallo. emerge -atv scipy failed with the following message: >>> Failed to emerge sci-libs/scipy-0.19.1-r1, Log file: >>> '/var/tmp/portage/sci-libs/scipy-0.19.1-r1/temp/build.log' * Messages for package sci-libs/scipy-0.19.1-r1: * ERROR: sci-libs/scipy-0.19.1-r1::science-kit failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 92: Called src_compile * environment, line 4389: Called distutils-r1_src_compile * environment, line 1317: Called _distutils-r1_run_foreach_impl 'python_compile' * environment, line 390: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile' * environment, line 3808: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile' * environment, line 2880: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile' * environment, line 2878: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile' * environment, line 883: Called distutils-r1_run_phase 'python_compile' * environment, line 1310: Called python_compile * environment, line 3396: Called distutils-r1_python_compile 'config_fc' '--noopt' '--noarch' * environment, line 1185: Called esetup.py 'build' 'config_fc' '--noopt' '--noarch' * environment, line 1889: Called die * The specific snippet of code: * "${@}" || die "${die_args[@]}"; * * If you need support, post the output of `emerge --info '=sci-libs/scipy-0.19.1-r1::science-kit'`, * the complete build log and the output of `emerge -pqv '=sci-libs/scipy-0.19.1-r1::science-kit'`. * The complete build log is located at '/var/tmp/portage/sci-libs/scipy-0.19.1-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sci-libs/scipy-0.19.1-r1/temp/environment'. * Working directory: '/var/tmp/portage/sci-libs/scipy-0.19.1-r1/work/scipy-0.19.1-python2_7' * S: '/var/tmp/portage/sci-libs/scipy-0.19.1-r1/work/scipy-0.19.1' * GNU info directory index is up-to-date. In the attachment you can find the output of : emerge --info '=sci-libs/scipy-0.19.1-r1::science-kit' An additional hint: I added one time in the /etc/ego.conf the python 3.kit. But i removed it. The reason was that i thought that this additional kit can be the reason for this issue. After I removed it, I executed emerge -auDN --newuse @world succesfully. emerge_info.txt