Building ktp-common-internals fails here because of a cmake-error: CMake Error at /usr/share/apps/cmake/modules/FindGettext.cmake:232 (ADD_CUSTOM_TARGET): add_custom_target cannot create target "pofiles" because another target po/ja/CMakeLists.txt:2 (GETTEXT_PROCESS_PO_FILES) CMake Error at /usr/share/apps/cmake/modules/FindGettext.cmake:232 (ADD_CUSTOM_TARGET): add_custom_target cannot create target "pofiles" because another target with the same name already exists. The existing target is a custom target created in source directory "/var/tmp/portage/net-im/ktp-common-internals-0.5.80/work/ktp-common-internals-0.5.80/po/de". See documentation for policy CMP0002 for more details. Call Stack (most recent call first): po/zh_CN/CMakeLists.txt:2 (GETTEXT_PROCESS_PO_FILES) Reproducible: Always Steps to Reproduce: 1. Run cmake on the 0.6 beta source. 2. 3. Actual Results: Configuring fails. Expected Results: Configuring does not fail. I use gentoo and tried to install it via kde overlay. The build log follows.
Created attachment 78132 [details] build log
Could you look at this bug: https://bugs.kde.org/show_bug.cgi?id=316308 and let me know if adding this line to cmake fixes it.
(In reply to comment #2) > Could you look at this bug: > https://bugs.kde.org/show_bug.cgi?id=316308 > > and let me know if adding this line to cmake fixes it. Yes, that fixes it. Sorry for not finding this bug earlier. :) From what I read in the other file it should affect all ktp-projects? Only ktp-common-internals's configuring seems to fail without this patch here. Should I mention the need of this patch in the gentoo community or is already taken care of it?
> From what I read in the other file it should affect all ktp-projects? Only ktp-common-internals's configuring seems to fail without this patch here. I thought it was all of them, let me check with the reporter of that bug. It's being taken care of by us for 0.6.0 (due at the end of the month) I don't plan on updating the betas, so if you want to fix the betas in Gentoo you will have to do it within your community. *** This bug has been marked as a duplicate of bug 316308 ***