-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
// Some comments here public String getFoo() {-isystem /usr/include/qt5/QtNetwork/5.15.2/QtNetwork -isystem /usr/include/qt5/QtCore/5.15.2 -isystem /usr/include/qt5/QtCore/5.15.2/QtCore -isystem /usr/include/KF5/KArchive -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KContacts -isystem /usr/include/qt5/QtGui -isystem /usr/include/KPim -isystem /usr/include/poppler -isystem /usr/include/KF5/KI18nLocaleData -isystem /usr/include/KF5/KCalendarCore -DQT_NO_DEBUG -DNDEBUG -march=skylake -O2 -pipe -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -pedantic -Wzero-as-null-pointer-constant -Wmissing-include-dirs -fdiagnostics-color=always -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=c++17 -MD -MT src/lib/CMakeFiles/KPimItinerary.dir/calendarhandler.cpp.o -MF src/lib/CMakeFiles/KPimItinerary.dir/calendarhandler.cpp.o.d -o src/lib/CMakeFiles/KPimItinerary.dir/calendarhandler.cpp.o -c /var/tmp/portage/kde-apps/kitinerary-22.04.1/work/kitinerary-22.04.1/src/lib/calendarhandler.cpp ninja: build stopped: subcommand failed. * ERROR: kde-apps/kitinerary-22.04.1::kde-kit failed (compile phase): * ninja -v -j4 -l0 failed * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 2665: Called kde5_src_compile * environment, line 2039: Called cmake-utils_src_compile * environment, line 983: Called cmake-utils_src_make * environment, line 1167: Called _cmake_ninja_src_make * environment, line 639: Called eninja * environment, line 1475: Called die * The specific snippet of code: * "$@" || die "${nonfatal_args[@]}" "${*} failed" * * If you need support, post the output of `emerge --info '=kde-apps/kitinerary-22.04.1::kde-kit'`, * the complete build log and the output of `emerge -pqv '=kde-apps/kitinerary-22.04.1::kde-kit'`. * The complete build log is located at '/var/tmp/portage/kde-apps/kitinerary-22.04.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-apps/kitinerary-22.04.1/temp/environment'. * Working directory: '/var/tmp/portage/kde-apps/kitinerary-22.04.1/work/kitinerary-22.04.1_build' * S: '/var/tmp/portage/kde-apps/kitinerary-22.04.1/work/kitinerary-22.04.1' >>> Failed to emerge kde-apps/kitinerary-22.04.1, Log file: >>> '/var/tmp/portage/kde-apps/kitinerary-22.04.1/temp/build.log' * Messages for package kde-apps/kitinerary-22.04.1: * ERROR: kde-apps/kitinerary-22.04.1::kde-kit failed (compile phase): * ninja -v -j4 -l0 failed * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 2665: Called kde5_src_compile * environment, line 2039: Called cmake-utils_src_compile * environment, line 983: Called cmake-utils_src_make * environment, line 1167: Called _cmake_ninja_src_make * environment, line 639: Called eninja * environment, line 1475: Called die * The specific snippet of code: * "$@" || die "${nonfatal_args[@]}" "${*} failed" * * If you need support, post the output of `emerge --info '=kde-apps/kitinerary-22.04.1::kde-kit'`, * the complete build log and the output of `emerge -pqv '=kde-apps/kitinerary-22.04.1::kde-kit'`. * The complete build log is located at '/var/tmp/portage/kde-apps/kitinerary-22.04.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-apps/kitinerary-22.04.1/temp/environment'. * Working directory: '/var/tmp/portage/kde-apps/kitinerary-22.04.1/work/kitinerary-22.04.1_build' * S: '/var/tmp/portage/kde-apps/kitinerary-22.04.1/work/kitinerary-22.04.1' mexwolf /home/mexwolf # return foo; }
- duplicates
-
FL-10922 Failed to emerge kde-apps/kitinerary-22.04.1
- Closed