From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] KDE 4.0 and dbus compile error
Date: Tue, 22 Jan 2008 08:42:08 -0600 [thread overview]
Message-ID: <479600C0.3020403@bellsouth.net> (raw)
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
next reply other threads:[~2008-01-22 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:42 Dale [this message]
2008-01-22 14:54 ` [gentoo-user] KDE 4.0 and dbus compile error James Ausmus
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=479600C0.3020403@bellsouth.net \
--to=dalek1967@bellsouth.net \
--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