From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] kdesdk-strigi-analyzer won't build
Date: Wed, 17 Sep 2008 15:54:25 -0400 [thread overview]
Message-ID: <48D16071.9050507@ercbroadband.org> (raw)
In-Reply-To: <d257c3560809171214k5e53536ge6a2ca03d7836c20@mail.gmail.com>
Beso wrote:
>>
>
> ok, i was making some confusion. i have strigi installed but not
> nepomuk. strigi has one problem. the old versions (0.5.10) might
> result too old for the kde 4.1.1, but the new version needs the latest
> cmake version (2.6.1) or else it won't build fine. so you should first
> ascertain that cmake 2.6.1 is installed and then try rebuilding
> strigi. strigi is one of the basic components required by
> systemsettings, kdelibs and plasma for the search to work. if you
> still cannot build it, then try adding the following line to your
> /etc/portage/package.mask:
>
> =app-misc/strigi-9999
>
> this will block the strigi live ebuild and try to build kde4 based on
> the old strigi, but i don't guarantee that it will work well with it.
>
Well, I tried that too. I did have cmake 2.6.1 on here, but didn't know
if strigi had been built with that version or not, so I went ahead and
rebuilt it. I still cannot get the other components (like
kdepim-strigi-analyzer) to build however.
It's frustrating, but I'll just build all of kde4 that I can now and
leave the rest until that gets fixed.
I may report the bug though, although will the Gentoo folks even look at
it if it's more an upstream thing from them?
--
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
next prev parent reply other threads:[~2008-09-17 19:55 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
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 [this message]
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=48D16071.9050507@ercbroadband.org \
--to=mhaney@ercbroadband.org \
--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