Beso wrote:
2008/9/16 <[EMAIL PROTECTED]>:
On Tuesday 16 September 2008 16:18:06 Mark Haney wrote:
I'm updating to KDE 4.1.1 today and all went well until
kdesdk-strigi-analyzer bombed with this:
/usr/include/strigi/streamendanalyzer.h:37: error: overriding 'virtual
signed char Strigi::StreamEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::InputStream*)'
make[2]: *** [strigi-analyzer/po/CMakeFiles/po.dir/poendanalyzer.o]
Error 1
make[1]: *** [strigi-analyzer/po/CMakeFiles/po.dir/all] Error 2
make: *** [all] Error 2
*
* ERROR: kde-base/kdesdk-strigi-analyzer-4.1.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2957: Called
kde4overlay-meta_src_compile
* environment, line 2311: Called
kde4overlay-meta_src_make
* environment, line 2360: Called
kde4overlay-base_src_make
* environment, line 2071: Called cmake-utils_src_make
* environment, line 723: Called die
* The specific snippet of code:
* emake "$@" || die "Make failed!";
I don't know what repository is that overlay uses, but it compiles fine(At
revision 861576) here(kde4-experimental) for quite a while now.
Is there a way to fix that? How do I continue to build kde-meta-4.1.1
if this one bombs? just emerge packages one at a time?
Sorry I could continue on advice you on migrating to kde4-experimental, since
a glitch like this could be avoided easy, but I don't want to start yet
another flame war, so I'll just keep quiet.
kde4-experimental is paludis overlay and goes with 4.2 developing
branch. the portage one goes with the 4.1 one for what i know.
How can I avoid having it included in the build? I tried removing
strigi, but checking on the next emerge kde-meta wants to include it.
That's aggravating.
--
Libenter homines id quod volunt credunt -- Caius Julius Caesar
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
