On a fresh complete build of kde-meta from stage3 pykde4 fails to build. The error message was: In file included from /usr/include/akonadi/item.h:28:0, from /usr/include/akonadi/monitor.h:24, from /usr/include/akonadi/changerecorder.h:23, from /var/tmp/portage/kde-base/pykde4-4.8.5/work/pykde4-4.8.5/sip /akonadi/agentfilterproxymodel.sip:35, from /var/tmp/portage/kde-base/pykde4-4.8.5/work/pykde4-4.8.5_bui ld-2.7/sip/akonadi/sipakonadipart0.cpp:7: /usr/include/akonadi/itempayloadinternals_p.h:29:32: fatal error: boost/shared_ptr .hpp: No such file or directory Complete logs attached. Scripts used to build this are available at: git://github.com/rich0/rich0-gentoo-bootstrap.git (branch rich0-changes using desktop plugin) I would think this should be reproducible from a stage3 if you sync, set USE, emerge -uDN world, and emerge kde-base. Error occurs on both x86 and amd64 builds. Reproducible: Always
Created attachment 327918 [details] build log
Created attachment 327920 [details] output of emerge --info '=kde-base/pykde4-4.8.5'
Created attachment 327922 [details] output of emerge -pqv '=kde-base/pykde4-4.8.5'
Created attachment 327924 [details] build environment
Created attachment 328800 [details] Same problem for different reasons : sip already defined Same problem for different reasons. Cf my attachments build.log and emerge--info_kde-base_pykde4-4.8.5.log : sip: /var/tmp/portage/kde-base/pykde4-4.8.5/work/pykde4-4.8.5/sip/kdecore/typedefs.sip:955: Mapped type has already been defined in another module make[2]: *** [sip/knewstuff/sipknewstuffpart0.cpp] Erreur 1 make[2] : on quitte le répertoire « /var/tmp/portage/kde-base/pykde4-4.8.5/work/pykde4-4.8.5_build-2.7 » make[1]: *** [CMakeFiles/python_module_PyKDE4_knewstuff.dir/all] Erreur 2
Created attachment 328802 [details] Same problem for different reasons : sip already defined - 2
(In reply to comment #5) > Same problem for different reasons : sip already defined Please file a separate bug for that.
This looks like bug #434144.
We are now tracking fast stabilisation of 4.9.3 (which contains a fix for this bug) in bug #442394.