Re: [gentoo-desktop] Dependencies of KDE 3

[Igor Korot <ikorot01@gmail.com>]

Hi,

On Tue, Nov 27, 2012 at 3:51 AM, E. Liddell <ejlddll@googlemail.com> wrote:
> On Mon, 26 Nov 2012 16:34:33 -0800
> Igor Korot <ikorot01@gmail.com> wrote:
>
>> Hi,
>> Well, it's kind of OK list... ;-)
>>
>>  * Messages for package kde-base/konq-plugins-3.5.10:
>>
>>  * emerge --keep-going: kde-base/konq-plugins-3.5.10 dropped due to
>>  * unsatisfied dependency.
>>  *
>>  * The following 21 packages have failed to build or install:
>>  *
> [...]
>>
>> What would be the first package to look at? (meaning most important one?)

First off, thank you for sorting things out.

>
> Let's see here.  Ignore packages with the -meta suffix, first off, since they're just
> aggregators for other packages.  Secondly, since Portage's dependency identification
> sometimes messes up in --keep-going runs, attempt to individually re-emerge
> any package that didn't get far enough to produce a log.  Start with the kde-base packages:
>
>>  *  (kde-base/kdm-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/kdebase-startkde-3.5.10-r5::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/konqueror-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/kdesktop-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/konsole-3.5.10::kde-sunset, ebuild scheduled for merge)
>
> Most of these packages are important to the basic functioning of KDE, and you need
> to get them merged if you want a functioning desktop.  Then look at the extras:

Here, unmasking kcontrol fixed everything. All 5 packages are now
compiled and installed
correctly.

>
>>  *  (kde-base/kmail-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/konqueror-akregator-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/konq-plugins-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/kontact-specialdates-3.5.10::kde-sunset, ebuild scheduled for merge)
>
> These packages are less important, and if you can live with the idea of using a
> different (probably GTK-based) mailer and calendar application, you don't
> absolutely need them.

Here only kontact-specialdates-3.5.10 remains as it depends on korganizer.
See below.

>
> For the remainder:
>
>>  *  (kde-base/kcontrol-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/ksvg-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/kopete-3.5.10-r5::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/kate-plugins-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/konsolekalendar-3.5.10::kde-sunset, ebuild scheduled for merge)
>>  *  (kde-base/korganizer-3.5.10::kde-sunset, ebuild scheduled for merge)
>
> and for any packages on the other lists that still won't merge, use the
> equery command to determine what the most recent KDE3 ebuild is:

This is an error on korganizer both 3.5.10 and 3.5.10-r1 (latest):

/bin/sh ../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../..
-I../../../kontact/interfaces -I../../../libkdepim
-I../../../korganizer -I../../../korganizer/interfaces -I../../..
-I../../../libkdepim -I/usr/kde/3.5/include -I/usr/qt/3/include -I.
-DQT_THREAD_SUPPORT  -D_REENTRANT -D_LARGE_FILES=1  -Wno-long-long
-Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
-Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2
-march=core2 -O2 -pipe -Wformat-security -Wmissing-format-attribute
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION  -c -o korganizerplugin.lo korganizerplugin.cpp
/bin/sh ../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../..
-I../../../kontact/interfaces -I../../../libkdepim
-I../../../korganizer -I../../../korganizer/interfaces -I../../..
-I../../../libkdepim -I/usr/kde/3.5/include -I/usr/qt/3/include -I.
-DQT_THREAD_SUPPORT  -D_REENTRANT -D_LARGE_FILES=1  -Wno-long-long
-Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
-Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2
-march=core2 -O2 -pipe -Wformat-security -Wmissing-format-attribute
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION  -c -o summarywidget.lo summarywidget.cpp
In file included from /usr/qt/3/include/qdragobject.h:50:0,
                 from korganizerplugin.cpp:28:
/usr/qt/3/include/qimage.h: In member function 'bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const':
/usr/qt/3/include/qimage.h:61:61: warning: suggest parentheses around
'&&' within '||'
summarywidget.cpp: In member function 'void SummaryWidget::updateView()':
summarywidget.cpp:170:64: error: cannot call constructor 'QDate::QDate' directly
summarywidget.cpp:170:64: error:   for a function-style cast, remove
the redundant '::QDate'
summarywidget.cpp:230:38: error: cannot call constructor 'QTime::QTime' directly
summarywidget.cpp:230:38: error:   for a function-style cast, remove
the redundant '::QTime'
summarywidget.cpp:233:40: error: cannot call constructor 'QTime::QTime' directly
summarywidget.cpp:233:40: error:   for a function-style cast, remove
the redundant '::QTime'
make[4]: *** [summarywidget.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory
`/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10/kontact/plugins/korganizer'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10/kontact/plugins'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10/kontact'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10'
make: *** [all] Error 2
emake failed
 * ERROR: kde-base/korganizer-3.5.10-r1 failed (compile phase):
 *   died running emake, kde_src_compile:make
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4738:  Called kde_src_compile
 *   environment, line 3342:  Called kde_src_compile 'all'
 *   environment, line 3357:  Called kde_src_compile 'make'
 *   environment, line 3349:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *
 * If you need support, post the output of `emerge --info
'=kde-base/korganizer-3.5.10-r1'`,
 * the complete build log and the output of `emerge -pqv
'=kde-base/korganizer-3.5.10-r1'`.
 * This ebuild used the following eclasses from overlays:
 *   /var/lib/layman/kde-sunset/eclass/kde-meta.eclass
 *   /var/lib/layman/kde-sunset/eclass/kde.eclass
 *   /var/lib/layman/kde-sunset/eclass/kde-functions.eclass
 *   /var/lib/layman/kde-sunset/eclass/qt3.eclass
 * This ebuild is from an overlay named 'kde-sunset':
'/var/lib/layman/kde-sunset/'
 * The complete build log is located at
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/temp/environment'.
 * Working directory:
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10'
 * S: '/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10'

>>> Failed to emerge kde-base/korganizer-3.5.10-r1, Log file:

>>>  '/var/tmp/portage/kde-base/korganizer-3.5.10-r1/temp/build.log'

 * Messages for package kde-base/korganizer-3.5.10-r1:

 * ERROR: kde-base/korganizer-3.5.10-r1 failed (compile phase):
 *   died running emake, kde_src_compile:make
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4738:  Called kde_src_compile
 *   environment, line 3342:  Called kde_src_compile 'all'
 *   environment, line 3357:  Called kde_src_compile 'make'
 *   environment, line 3349:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *
 * If you need support, post the output of `emerge --info
'=kde-base/korganizer-3.5.10-r1'`,
 * the complete build log and the output of `emerge -pqv
'=kde-base/korganizer-3.5.10-r1'`.
 * This ebuild used the following eclasses from overlays:
 *   /var/lib/layman/kde-sunset/eclass/kde-meta.eclass
 *   /var/lib/layman/kde-sunset/eclass/kde.eclass
 *   /var/lib/layman/kde-sunset/eclass/kde-functions.eclass
 *   /var/lib/layman/kde-sunset/eclass/qt3.eclass
 * This ebuild is from an overlay named 'kde-sunset':
'/var/lib/layman/kde-sunset/'
 * The complete build log is located at
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/temp/environment'.
 * Working directory:
'/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10'
 * S: '/var/tmp/portage/kde-base/korganizer-3.5.10-r1/work/korganizer-3.5.10'

Any idea?

I will try to merge everything else one by one and report back any
other problems.

Thank you.

>
> # equery meta kcontrol
>  * kde-base/kcontrol [gentoo]
> Herd:        kde (kde@gentoo.org)
> Maintainer:  None specified
> Upstream:    None specified
> Homepage:    http://www.kde.org/
> Location:    /usr/portage/kde-base/kcontrol
> Keywords:    3.5.10:3.5: alpha amd64 hppa ia64 ppc ppc64 sparc x86
> Keywords:    3.5.10-r1:3.5: ~alpha ~amd64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd <--this one
> Keywords:    4.8.5:4: amd64 ppc x86 ~ppc64 ~x86-fbsd
> Keywords:    4.9.1:4:
> Keywords:    4.9.2:4: ~amd64 ~amd64-linux ~arm ~x86 ~x86-linux
>
> and unmask it, then try to merge again.  If you don't have the equery command,
> emerge gentoolkit.
>
> The packages you absolutely need to get working are the ones I shortlisted as part
> of kde-base, and kcontrol.  Most of the others can be worked around by substituting
> other applications with the same functionality.  Note that kopete has at least one
> broken plugin (I think it's jabber) that may not compile under any circumstances.
>
> Oh, and incidentally,
>
> No.
>>Should I top-post?
>
> Good luck.
>