Here is what emerge say's when I will/want to compile the package, -- Configuring done -- Generating done -- Build files have been written to: /var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80_build >>> Source configured. >>> Compiling source in /var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80 ... >>> Working in BUILD_DIR: "/var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80_build" make -j1 Scanning dependencies of target kabcclient_automoc Generating kabcclient.moc [ 0%] Built target kabcclient_automoc Scanning dependencies of target kabcclient [ 6%] Building CXX object console/kabcclient/src/CMakeFiles/kabcclient.dir/kabcclient_automoc.o [ 12%] Building CXX object console/kabcclient/src/CMakeFiles/kabcclient.dir/main.o /var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80/console/kabcclient/src/main.cpp: In function 'int main(int, char**)': /var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80/console/kabcclient/src/main.cpp:120: error: no matching function for call to 'KCmdLineOptions::add(KLocalizedString, KLocalizedString)' /usr/include/kcmdlineargs.h:121: note: candidates are: KCmdLineOptions& KCmdLineOptions::add(const QByteArray&, const KLocalizedString&, const QByteArray&) /usr/include/kcmdlineargs.h:130: note: KCmdLineOptions& KCmdLineOptions::add(const KCmdLineOptions&) make[2]: *** [console/kabcclient/src/CMakeFiles/kabcclient.dir/main.o] Error 1 make[1]: *** [console/kabcclient/src/CMakeFiles/kabcclient.dir/all] Error 2 make: *** [all] Error 2 * ERROR: kde-base/kabcclient-4.6.80 failed (compile phase): * emake failed * * If you need support, post the output of 'emerge --info =kde-base/kabcclient-4.6.80', * the complete build log and the output of 'emerge -pqv =kde-base/kabcclient-4.6.80'. * This ebuild is from an overlay named 'kde': '/var/lib/layman/kde/' * The complete build log is located at '/var/tmp/portage/kde-base/kabcclient-4.6.80/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/kabcclient-4.6.80/temp/environment'. * S: '/var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80' >>> Failed to emerge kde-base/kabcclient-4.6.80, Log file: >>> '/var/tmp/portage/kde-base/kabcclient-4.6.80/temp/build.log' * Messages for package kde-base/kabcclient-4.6.80: * ERROR: kde-base/kabcclient-4.6.80 failed (compile phase): * emake failed * * If you need support, post the output of 'emerge --info =kde-base/kabcclient-4.6.80', * the complete build log and the output of 'emerge -pqv =kde-base/kabcclient-4.6.80'. * This ebuild is from an overlay named 'kde': '/var/lib/layman/kde/' * The complete build log is located at '/var/tmp/portage/kde-base/kabcclient-4.6.80/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/kabcclient-4.6.80/temp/environment'. * S: '/var/tmp/portage/kde-base/kabcclient-4.6.80/work/kabcclient-4.6.80' I hope this is the right place for this Bug-Report, because I can't find an special/external BugTracker for ebuilds from KDE-Overlay. It is not realy an eBuild error, because the Error is inside of the Version of the Source-Package "kabacclient-4.6.80".
Created attachment 275397 [details, diff] patch for main.cpp Line 120 copy the patch to: /var/lib/layman/kde/kde-base/kabcclient/files/
Created attachment 275399 [details] ebuild with the usage of my patch overwrite the ebuild file "kabcclient-4.6.80.ebuild" in /var/lib/layman/kde/kde-base/kabcclient with this one. Change into the dir "" and run "ebuild kabcclient-4.6.80.ebuild manifest" after this you can run "ebuild kabcclient-4.6.80.ebuild prepare" to see if the patch applies. (to Check before you again emerge;) ) If you had already runned emerge -av @kde-4.7 (or similary), you have to clean first the unpack/tmp of this package. to Do, run "rm -rf /var/tmp/portage/kde-base/kabcclient-4.6.80/" and then check with "ebuild kabcclient-4.6.80.ebuild prepare" if the patch applies. Now you can re-emerge or resume "emerge --resume" your last emerge process.
I have writen an Patch and modified the ebuild file, I have added both here. You can check the Detail Page of both Attachements for instructions.
