[gentoo-user] KDE 4.0 and dbus compile error

[gentoo-user] KDE 4.0 and dbus compile error

[Dale]

Hi,

I started my emerge of KDE 4.0 a while ago and I keep getting this error:

> >>> Emerging (1 of 177) app-misc/strigi-0.5.7 to /
>  * strigi-0.5.7.tar.bz2 RMD160 SHA1 SHA256 size ;-)
> ...                                [ ok ]
>  * checking ebuild checksums ;-)
> ...                                                   [ ok ]
>  * checking auxfile checksums ;-)
> ...                                                  [ ok ]
>  * checking miscfile checksums ;-)
> ...                                                 [ ok ]
>  * checking strigi-0.5.7.tar.bz2 ;-)
> ...                                               [ ok ]
>
>  * You are building Strigi with qt4 but without dbus.
>  * Strigiclient needs dbus to detect a running Strigi daemon.
>  * Please enable both qt4 and dbus.
>
>  *
>  * ERROR: app-misc/strigi-0.5.7 failed.
>  * Call stack:
>  *               ebuild.sh, line   46:  Called pkg_setup
>  *     strigi-0.5.7.ebuild, line   62:  Called die
>  * The specific snippet of code:
>  *              die
>  *  The die message:
>  *   (no error message)
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/log/portage/app-misc:strigi-0.5.7:20080122-143048.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
>  *
>
>  * Messages for package app-misc/strigi-0.5.7:
>
>  * You are building Strigi with qt4 but without dbus.
>  * Strigiclient needs dbus to detect a running Strigi daemon.
>  * Please enable both qt4 and dbus.
>  *
>  * ERROR: app-misc/strigi-0.5.7 failed.
>  * Call stack:
>  *               ebuild.sh, line   46:  Called pkg_setup
>  *     strigi-0.5.7.ebuild, line   62:  Called die
>  * The specific snippet of code:
>  *              die
>  *  The die message:
>  *   (no error message)
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/log/portage/app-misc:strigi-0.5.7:20080122-143048.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
>  *
>
> root@smoker / #   
Here is my emerge info USE info: 

> root@smoker / # emerge --info | grep USE
> USE="3dnow X acl acpi alsa amd arts artswrappersuid automount berkdb
> bitmap-fonts browserplugin bzip2 cairo cddb cdr chroot cli cracklib
> crypt cups curl dbus dri dvd dvdr dvdread eds emboss encode esd exif
> fam fdftk fortran gaim gdbm gif gimp gimpprint gkrellm gphoto2 gpm
> gstreamer gtk hal hbci iconv ipv6 isdnlog java javascript jbig jpeg
> jpeg2k justify kde ldap libwww logrotate mad midi mikmod mmx mp3 mpeg
> mudflap ncurses nptl nptlonly nsplugin offensive ofx ogg opengl openmp
> pam pcre pdf perl png ppds pppd python qt3 qt4 quicktime readline
> realmedia reflection sdl seamonkey session spell spl sqlite sse ssl
> syslog tcl tcpd tiff tk truetype truetype-fonts type1-fonts udev
> unicode usb vorbis win32codecs wma wmf wmp x86 xml xorg xprint xv
> yahoo zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym
> copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
> lfloat linear meter mulaw multi null plug rate route share shm
> softvol" APACHE2_MODULES="actions alias auth_basic authn_alias
> authn_anon authn_dbm authn_default authn_file authz_dbm authz_default
> authz_groupfile authz_host authz_owner authz_user autoindex cache dav
> dav_fs dav_lock deflate dir disk_cache env expires ext_filter
> file_cache filter headers include info log_config logio mem_cache mime
> mime_magic negotiation rewrite setenvif speling status unique_id
> userdir usertrack vhost_alias" CAMERAS="canon" ELIBC="glibc"
> INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad
> cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
> LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="nvidia"
> root@smoker / #  

I have dbus and qt4 in there and have had it for quite a while if I
recall correctly.  Here is the flag info for the specific packages:

> root@smoker / # emerge -vp qt
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   ] x11-libs/qt-4.4.0_rc1  USE="opengl -qt3support" 0 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
> root@smoker / # emerge -pv strigi
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N    ] app-misc/strigi-0.5.7  USE="clucene dbus exiv2 java
> qt4 -debug -hyperestraier -inotify -test" 0 kB
>
> Total: 1 package (1 new), Size of downloads: 0 kB
> root@smoker / # 

Note that dbus is not included in qt4 and is not even a option.  What's
up with that you reckon?

I also get this when doing a emerge -uvDN world:

> >>> Emerging (1 of 177) app-misc/strigi-0.5.7 to /
>  * strigi-0.5.7.tar.bz2 RMD160 SHA1 SHA256 size ;-)
> ...                                [ ok ]
>  * checking ebuild checksums ;-)
> ...                                                   [ ok ]
>  * checking auxfile checksums ;-)
> ...                                                  [ ok ]
>  * checking miscfile checksums ;-)
> ...                                                 [ ok ]
>  * checking strigi-0.5.7.tar.bz2 ;-)
> ...                                               [ ok ]
>  *
>  * ERROR: app-misc/strigi-0.5.7 failed.
>  * Call stack:
>  *               ebuild.sh, line   46:  Called pkg_setup
>  *     strigi-0.5.7.ebuild, line   48:  Called built_with_use
> 'pkg_setup' 'pkg_setup'
>  *           eutils.eclass, line 1694:  Called die
>  * The specific snippet of code:
>  *                                      die)   die "$PKG does not
> actually support the $1 USE flag!";;
>  *  The die message:
>  *   x11-libs/qt-4.4.0_rc1 does not actually support the dbus USE flag!
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/log/portage/app-misc:strigi-0.5.7:20080122-143912.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
>  *
>
>  * Messages for package app-misc/strigi-0.5.7:
>
>  *
>  * ERROR: app-misc/strigi-0.5.7 failed.
>  * Call stack:
>  *               ebuild.sh, line   46:  Called pkg_setup
>  *     strigi-0.5.7.ebuild, line   48:  Called built_with_use
> 'pkg_setup' 'pkg_setup'
>  *           eutils.eclass, line 1694:  Called die
>  * The specific snippet of code:
>  *                                      die)   die "$PKG does not
> actually support the $1 USE flag!";;
>  *  The die message:
>  *   x11-libs/qt-4.4.0_rc1 does not actually support the dbus USE flag!
>  *
>  * If you need support, post the topmost build error, and the call
> stack if relevant.
>  * A complete build log is located at
> '/var/log/portage/app-misc:strigi-0.5.7:20080122-143912.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
>  *
> root@smoker / # 

Any ideas?  Am I missing something?  Need more info, let me know.

Dale

:-)  :-) 

-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[James Ausmus]

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

Re: [gentoo-user] KDE 4.0 and dbus compile error

[pu stshine]

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

use qt-4.3.3.   4.4.0 is not OK yet.

2008/1/22, James Ausmus <james.ausmus@gmail.com>:
>
> 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
>
>

[-- Attachment #2: Type: text/html, Size: 1911 bytes --]

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Jerry McBride]

On Tuesday 22 January 2008 09:42:08 am Dale wrote:
> Hi,
>
> I started my emerge of KDE 4.0 a while ago and I keep getting this error:
> > >>> Emerging (1 of 177) app-misc/strigi-0.5.7 to /
> >
> >  * strigi-0.5.7.tar.bz2 RMD160 SHA1 SHA256 size ;-)
> > ...                                [ ok ]
> >  * checking ebuild checksums ;-)
> > ...                                                   [ ok ]
> >  * checking auxfile checksums ;-)
> > ...                                                  [ ok ]
> >  * checking miscfile checksums ;-)
> > ...                                                 [ ok ]
> >  * checking strigi-0.5.7.tar.bz2 ;-)
> > ...                                               [ ok ]
> >
> >  * You are building Strigi with qt4 but without dbus.
> >  * Strigiclient needs dbus to detect a running Strigi daemon.
> >  * Please enable both qt4 and dbus.
> >
> >  *
> >  * ERROR: app-misc/strigi-0.5.7 failed.
> >  * Call stack:
> >  *               ebuild.sh, line   46:  Called pkg_setup
> >  *     strigi-0.5.7.ebuild, line   62:  Called die
> >  * The specific snippet of code:
> >  *              die
> >  *  The die message:
> >  *   (no error message)
> >  *
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located at
> > '/var/log/portage/app-misc:strigi-0.5.7:20080122-143048.log'.
> >  * The ebuild environment file is located at
> > '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
> >  *
> >
> >  * Messages for package app-misc/strigi-0.5.7:
> >
> >  * You are building Strigi with qt4 but without dbus.
> >  * Strigiclient needs dbus to detect a running Strigi daemon.
> >  * Please enable both qt4 and dbus.
> >  *
> >  * ERROR: app-misc/strigi-0.5.7 failed.
> >  * Call stack:
> >  *               ebuild.sh, line   46:  Called pkg_setup
> >  *     strigi-0.5.7.ebuild, line   62:  Called die
> >  * The specific snippet of code:
> >  *              die
> >  *  The die message:
> >  *   (no error message)
> >  *
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located at
> > '/var/log/portage/app-misc:strigi-0.5.7:20080122-143048.log'.
> >  * The ebuild environment file is located at
> > '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
> >  *
> >
> > root@smoker / #
>
> Here is my emerge info USE info:
> > root@smoker / # emerge --info | grep USE
> > USE="3dnow X acl acpi alsa amd arts artswrappersuid automount berkdb
> > bitmap-fonts browserplugin bzip2 cairo cddb cdr chroot cli cracklib
> > crypt cups curl dbus dri dvd dvdr dvdread eds emboss encode esd exif
> > fam fdftk fortran gaim gdbm gif gimp gimpprint gkrellm gphoto2 gpm
> > gstreamer gtk hal hbci iconv ipv6 isdnlog java javascript jbig jpeg
> > jpeg2k justify kde ldap libwww logrotate mad midi mikmod mmx mp3 mpeg
> > mudflap ncurses nptl nptlonly nsplugin offensive ofx ogg opengl openmp
> > pam pcre pdf perl png ppds pppd python qt3 qt4 quicktime readline
> > realmedia reflection sdl seamonkey session spell spl sqlite sse ssl
> > syslog tcl tcpd tiff tk truetype truetype-fonts type1-fonts udev
> > unicode usb vorbis win32codecs wma wmf wmp x86 xml xorg xprint xv
> > yahoo zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym
> > copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
> > lfloat linear meter mulaw multi null plug rate route share shm
> > softvol" APACHE2_MODULES="actions alias auth_basic authn_alias
> > authn_anon authn_dbm authn_default authn_file authz_dbm authz_default
> > authz_groupfile authz_host authz_owner authz_user autoindex cache dav
> > dav_fs dav_lock deflate dir disk_cache env expires ext_filter
> > file_cache filter headers include info log_config logio mem_cache mime
> > mime_magic negotiation rewrite setenvif speling status unique_id
> > userdir usertrack vhost_alias" CAMERAS="canon" ELIBC="glibc"
> > INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad
> > cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
> > LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="nvidia"
> > root@smoker / #
>
> I have dbus and qt4 in there and have had it for quite a while if I
>
> recall correctly.  Here is the flag info for the specific packages:
> > root@smoker / # emerge -vp qt
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild   R   ] x11-libs/qt-4.4.0_rc1  USE="opengl -qt3support" 0 kB
> >
> > Total: 1 package (1 reinstall), Size of downloads: 0 kB
> > root@smoker / # emerge -pv strigi
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild  N    ] app-misc/strigi-0.5.7  USE="clucene dbus exiv2 java
> > qt4 -debug -hyperestraier -inotify -test" 0 kB
> >
> > Total: 1 package (1 new), Size of downloads: 0 kB
> > root@smoker / #
>
> Note that dbus is not included in qt4 and is not even a option.  What's
> up with that you reckon?
>
> I also get this when doing a emerge -uvDN world:
> > >>> Emerging (1 of 177) app-misc/strigi-0.5.7 to /
> >
> >  * strigi-0.5.7.tar.bz2 RMD160 SHA1 SHA256 size ;-)
> > ...                                [ ok ]
> >  * checking ebuild checksums ;-)
> > ...                                                   [ ok ]
> >  * checking auxfile checksums ;-)
> > ...                                                  [ ok ]
> >  * checking miscfile checksums ;-)
> > ...                                                 [ ok ]
> >  * checking strigi-0.5.7.tar.bz2 ;-)
> > ...                                               [ ok ]
> >  *
> >  * ERROR: app-misc/strigi-0.5.7 failed.
> >  * Call stack:
> >  *               ebuild.sh, line   46:  Called pkg_setup
> >  *     strigi-0.5.7.ebuild, line   48:  Called built_with_use
> > 'pkg_setup' 'pkg_setup'
> >  *           eutils.eclass, line 1694:  Called die
> >  * The specific snippet of code:
> >  *                                      die)   die "$PKG does not
> > actually support the $1 USE flag!";;
> >  *  The die message:
> >  *   x11-libs/qt-4.4.0_rc1 does not actually support the dbus USE flag!
> >  *
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located at
> > '/var/log/portage/app-misc:strigi-0.5.7:20080122-143912.log'.
> >  * The ebuild environment file is located at
> > '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
> >  *
> >
> >  * Messages for package app-misc/strigi-0.5.7:
> >
> >  *
> >  * ERROR: app-misc/strigi-0.5.7 failed.
> >  * Call stack:
> >  *               ebuild.sh, line   46:  Called pkg_setup
> >  *     strigi-0.5.7.ebuild, line   48:  Called built_with_use
> > 'pkg_setup' 'pkg_setup'
> >  *           eutils.eclass, line 1694:  Called die
> >  * The specific snippet of code:
> >  *                                      die)   die "$PKG does not
> > actually support the $1 USE flag!";;
> >  *  The die message:
> >  *   x11-libs/qt-4.4.0_rc1 does not actually support the dbus USE flag!
> >  *
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located at
> > '/var/log/portage/app-misc:strigi-0.5.7:20080122-143912.log'.
> >  * The ebuild environment file is located at
> > '/var/tmp/portage/app-misc/strigi-0.5.7/temp/die.env'.
> >  *
> > root@smoker / #
>
> Any ideas?  Am I missing something?  Need more info, let me know.
>
> Dale
>
> :-)  :-)

Hey Dale... morning....

I don't even have a qt in my make.conf, yet eix confirms that I have both qt 
3.x.x and qt 4.3.x installed (most recent versions). The KDE 4.0 docs say 
they don't yet support qt 4.4.x... So... if this was my box... I'd dump qt3 
and qt4 from USE and add back in just "qt". Dump qt 4.4.x. Then emerge the 
latest versions of qt4.3.x and qt3.x.x. Then revdep-rebuild to see what needs 
re-emerging... Then make a second run on those kd4.0 sources...

You're going to have to rebuild everything built against those qt4.4.x 
libraries... Yuk...

Cheers.... Yeah, left out a lot of detail there, too busy to flesh this 
out.... Work sucks!

If you want to verify what the heck I'm talking about... try eix -I qt, eix -I 
qt3, eix -I qt4 and eix -I qt3-core on your box to see what's using what 
before you start chopping... And "YES" I run an ~x86 box here.

-- 


From the Desk of: Jerome D. McBride
--
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Dale]

pu stshine wrote:
> use qt-4.3.3.   4.4.0 is not OK yet.
>
>

Well crap, another 5 hour download.  LOL 

See ya'll tomorrow. 

Dale

:-)  :-) 
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Eddie Mihalow Jr]

pu stshine wrote:
> use qt-4.3.3.   4.4.0 is not OK yet.
> 
> 2008/1/22, James Ausmus <james.ausmus@gmail.com 
> <mailto:james.ausmus@gmail.com>>:
> 
>     On Jan 22, 2008 6:42 AM, Dale <dalek1967@bellsouth.net
>     <mailto: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 <mailto:gentoo-user@lists.gentoo.org>
>     mailing list
> 
> 
What he said-4.3.3-QT and you have to add the 
"accessibility" flag also.

-- 
Edward A Mihalow Jr
Gentoo! Linux
Mudbug Computers and Networks
Registered Linux User#225662
New Orleans,LA
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Dale]

Eddie Mihalow Jr wrote:
> pu stshine wrote:
>> use qt-4.3.3.   4.4.0 is not OK yet.
>>
>> 2008/1/22, James Ausmus <james.ausmus@gmail.com
>> <mailto:james.ausmus@gmail.com>>:
>>
>>     On Jan 22, 2008 6:42 AM, Dale <dalek1967@bellsouth.net
>>     <mailto: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 <mailto:gentoo-user@lists.gentoo.org>
>>     mailing list
>>
>>
> What he said-4.3.3-QT and you have to add the "accessibility" flag also.
>

OK.  Got that done too.  Still downloading by the way.  :/

Also, I didn't have qt 4.4 installed before.  It was unmasked and pulled
in when I ran autounmask and emerge -uvDN world.  Is that going to be a
problem for others?

Dale

:-)  :_) 
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Dale]

Dale wrote:
>
> OK.  Got that done too.  Still downloading by the way.  :/
>
> Also, I didn't have qt 4.4 installed before.  It was unmasked and pulled
> in when I ran autounmask and emerge -uvDN world.  Is that going to be a
> problem for others?
>
> Dale
>
> :-)  :_) 
>   

Well, now I get this:

> [blocks B     ] <=x11-libs/qt-4.4_rc:4 (is blocking
> x11-libs/qt-core-4.4.0_rc1)
>
> Total: 187 packages (1 upgrade, 63 new, 122 in new slots, 1 reinstall,
> 1 block), Size of downloads: 0 kB
> root@smoker / #

Funny thing is, I don't have qt-4.4 installed, I don't guess anyway.

> root@smoker / # equery list qt
> [ Searching for package 'qt' in all categories among: ]
>  * installed packages
> [I--] [  ] dev-libs/dbus-qt3-old-0.70 (0)
> [I--] [M ] x11-libs/qt-3.3.8-r4 (3)
> [I--] [  ] x11-libs/qt-4.3.2-r1 (4)
> root@smoker / # 

Now what?  Can I shoot it?  LOL

Dale

:-)  :-) 


-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] KDE 4.0 and dbus compile error

[Dale]

Dale wrote:
> Dale wrote:
>   
>> OK.  Got that done too.  Still downloading by the way.  :/
>>
>> Also, I didn't have qt 4.4 installed before.  It was unmasked and pulled
>> in when I ran autounmask and emerge -uvDN world.  Is that going to be a
>> problem for others?
>>
>> Dale
>>
>> :-)  :_) 
>>   
>>     
>
> Well, now I get this:
>
>   
>> [blocks B     ] <=x11-libs/qt-4.4_rc:4 (is blocking
>> x11-libs/qt-core-4.4.0_rc1)
>>
>> Total: 187 packages (1 upgrade, 63 new, 122 in new slots, 1 reinstall,
>> 1 block), Size of downloads: 0 kB
>> root@smoker / #
>>     
>
> Funny thing is, I don't have qt-4.4 installed, I don't guess anyway.
>
>   
>> root@smoker / # equery list qt
>> [ Searching for package 'qt' in all categories among: ]
>>  * installed packages
>> [I--] [  ] dev-libs/dbus-qt3-old-0.70 (0)
>> [I--] [M ] x11-libs/qt-3.3.8-r4 (3)
>> [I--] [  ] x11-libs/qt-4.3.2-r1 (4)
>> root@smoker / # 
>>     
>
> Now what?  Can I shoot it?  LOL
>
> Dale
>
> :-)  :-) 
>
>
>   

Ooooops, never mind.  Autounmask had it on the bottom and I missed it. 
I guess portage remembers the last thing it reads. 

Here we go, I hope.

Dale

:-)  :-) 
-- 
gentoo-user@lists.gentoo.org mailing list