From: cuciferus@gmail.com
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] kdesdk-strigi-analyzer won't build
Date: Tue, 16 Sep 2008 17:17:15 +0300 [thread overview]
Message-ID: <200809161717.16727.cuciferus@gmail.com> (raw)
In-Reply-To: <48CFB20E.8080802@ercbroadband.org>
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.
next prev parent reply other threads:[~2008-09-16 14:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 13:18 [gentoo-amd64] kdesdk-strigi-analyzer won't build Mark Haney
2008-09-16 13:57 ` Beso
2008-09-16 14:04 ` Mark Haney
2008-09-16 14:17 ` Beso
2008-09-16 14:17 ` cuciferus [this message]
2008-09-16 14:19 ` Beso
2008-09-16 14:21 ` Mark Haney
2008-09-16 14:27 ` Beso
2008-09-16 15:12 ` Mark Haney
2008-09-16 15:31 ` Beso
2008-09-16 15:39 ` Mark Haney
2008-09-16 15:46 ` Beso
2008-09-16 17:53 ` Mark Haney
2008-09-16 18:44 ` Beso
2008-09-17 14:41 ` Mark Haney
2008-09-17 15:09 ` Beso
2008-09-17 15:17 ` Mark Haney
2008-09-17 16:03 ` Jan Jitse Venselaar
2008-09-17 16:05 ` Mark Haney
2008-09-17 16:45 ` Jan Jitse Venselaar
2008-09-17 19:14 ` Beso
2008-09-17 19:54 ` Mark Haney
2008-09-17 20:10 ` Beso
2008-09-17 21:12 ` [gentoo-amd64] " Duncan
2008-09-16 23:06 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200809161717.16727.cuciferus@gmail.com \
--to=cuciferus@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox