From: "James Ausmus" <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 4.0 and dbus compile error
Date: Tue, 22 Jan 2008 06:54:33 -0800 [thread overview]
Message-ID: <b79f23070801220654y29f8f586s6e6b5557c293c8b3@mail.gmail.com> (raw)
In-Reply-To: <479600C0.3020403@bellsouth.net>
On Jan 22, 2008 6:42 AM, Dale <dalek1967@bellsouth.net> wrote:
> Hi,
>
> I started my emerge of KDE 4.0 a while ago and I keep getting this error:
<snip>
> > * You are building Strigi with qt4 but without dbus.
> > * Strigiclient needs dbus to detect a running Strigi daemon.
> > * Please enable both qt4 and dbus.
> >
<snip>
Hi Dale-
I didn't get this error specifically when I was compiling kde 4.0 with
qt 4.4.0 (I might have upgraded to qt 4.4 after I had already compiled
strigi), but I know that, right now, the changes in the qt 4.4 API
aren't supported by (at least) several of the KDE 4.0 packages - they
just won't compile with it. Also, many of the ebuilds that check *how*
qt is built before compiling do *not* yet support the way that qt 4.4
has been split out into several packages (do an eix -I qt- to see all
the packages that qt has been split to in addition to just
x11-libs/qt) - in short, I had to re-mask qt 4.4 and downgrade before
I could continue installing kde 4.0 - the qt 4.4 and kde 4.0 just
aren't quite ready to mix yet (and qt 4.4 isn't quite ready to mix w/
Gentoo yet, either - there'll have to be a fair amount of ebuild
changes to other packages to support it).
HTH-
James
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-22 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:42 [gentoo-user] KDE 4.0 and dbus compile error Dale
2008-01-22 14:54 ` James Ausmus [this message]
2008-01-22 15:08 ` pu stshine
2008-01-22 15:31 ` Dale
2008-01-22 20:48 ` Eddie Mihalow Jr
2008-01-22 21:06 ` Dale
2008-01-23 12:54 ` Dale
2008-01-23 12:57 ` Dale
2008-01-22 15:20 ` Jerry McBride
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=b79f23070801220654y29f8f586s6e6b5557c293c8b3@mail.gmail.com \
--to=james.ausmus@gmail.com \
--cc=gentoo-user@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