Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Gentoo: Desktop

Dependencies of KDE 3

 

 

First page Previous page 1 2 Next page Last page  View All Gentoo desktop RSS feed   Index | Next | Previous | View Threaded


ikorot01 at gmail

Nov 20, 2012, 5:38 PM

Post #1 of 34 (3097 views)
Permalink
Dependencies of KDE 3

Hi, ALL,
I'm trying to install KDE 3 from kde-sunset overlay and am getting the
compiler error:


/bin/sh ../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop
-I../../kdecore -I. -I../../kjs -I../../kdecore/network
-I../../kwallet/client -I../../dcop -I../../libltdl -I../../kdefx
-I../../kdecore -I../../kdecore -I../../kdecore/network -I../../kdeui
-I../../kio -I../../kio/kio -I../../kio/kfile -I../..
-I/usr/qt/3/include -I. -I/usr/kde/3.5/include -DQT_THREAD_SUPPORT
-D_REENTRANT -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 ksslsettings.lo
ksslsettings.cc
In file included from ksslsettings.cc:47:0:
./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
./kopenssl.h:526:16: error: expected ';' before '(' token
./kopenssl.h:532:17: error: 'STACK' has not been declared
./kopenssl.h:538:15: error: 'STACK' has not been declared
./kopenssl.h:544:18: error: expected ';' before '(' token
./kopenssl.h:550:4: error: 'STACK' does not name a type
./kopenssl.h:556:16: error: 'STACK' has not been declared
./kopenssl.h:562:4: error: 'STACK' does not name a type
./kopenssl.h:828:4: error: 'STACK' does not name a type
./kopenssl.h:829:25: error: 'STACK' has not been declared
ksslsettings.cc: In member function 'QString KSSLSettings::getCipherList()':
ksslsettings.cc:157:12: error: no matching function for call to
'KOpenSSLProxy::sk_num(_STACK*)'
./kopenssl.h:538:8: note: candidate is: int KOpenSSLProxy::sk_num(int*)
ksslsettings.cc:159:20: error: 'class KOpenSSLProxy' has no member
named 'sk_value'
make[5]: *** [ksslsettings.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
In file included from kssl.cc:47:0:
./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
./kopenssl.h:526:16: error: expected ';' before '(' token
./kopenssl.h:532:17: error: 'STACK' has not been declared
./kopenssl.h:538:15: error: 'STACK' has not been declared
./kopenssl.h:544:18: error: expected ';' before '(' token
./kopenssl.h:550:4: error: 'STACK' does not name a type
./kopenssl.h:556:16: error: 'STACK' has not been declared
./kopenssl.h:562:4: error: 'STACK' does not name a type
./kopenssl.h:828:4: error: 'STACK' does not name a type
./kopenssl.h:829:25: error: 'STACK' has not been declared
kssl.cc: In member function 'void KSSL::setPeerInfo()':
kssl.cc:616:8: error: 'class KOpenSSLProxy' has no member named 'sk_dup'
make[5]: *** [kssl.lo] Error 1
make[5]: Leaving directory
`/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
make: *** [all] Error 2
emake failed
* ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
* died running emake, kde_src_compile:make
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4608: Called kde_src_compile
* environment, line 3187: Called kde_src_compile 'all'
* environment, line 3202: Called kde_src_compile 'make'
* environment, line 3194: 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/kdelibs-3.5.10-r6'`,
* the complete build log and the output of `emerge -pqv
'=kde-base/kdelibs-3.5.10-r6'`.
* This ebuild used the following eclasses from overlays:
* /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/kdelibs-3.5.10-r6/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
* Working directory:
'/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
* S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'

>>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file:

>>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log'

* Messages for package kde-base/kdelibs-3.5.10-r6:

* You have the legacyssl use flag enabled, which fixes issues with some broken
* sites, but breaks others instead. It is strongly discouraged to use it.
* For more information, see bug #128922.
* On some setups, which rely on the correct update of utmp records, not using
* utempter might not update them correctly. If you experience unexpected
* behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled.
* ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
* died running emake, kde_src_compile:make
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4608: Called kde_src_compile
* environment, line 3187: Called kde_src_compile 'all'
* environment, line 3202: Called kde_src_compile 'make'
* environment, line 3194: 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/kdelibs-3.5.10-r6'`,
* the complete build log and the output of `emerge -pqv
'=kde-base/kdelibs-3.5.10-r6'`.
* This ebuild used the following eclasses from overlays:
* /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/kdelibs-3.5.10-r6/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
* Working directory:
'/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
* S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'

Also, very strange thing is that the dependency tree of KDE 3 is not updated:

If I have the latest openssl, which is 1.0.0j, KDE will slot-instal 0.0.8x.

Is there such an incompatibility?

And third issue:

mDNSResponder ebuuild is not in the tree.

Could someone please put it back?

Thank you.


caneko at gmail

Nov 20, 2012, 7:12 PM

Post #2 of 34 (2973 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
> Hi, ALL,
> I'm trying to install KDE 3 from kde-sunset overlay and am getting the
> compiler error:
>
>
> /bin/sh ../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop
> -I../../kdecore -I. -I../../kjs -I../../kdecore/network
> -I../../kwallet/client -I../../dcop -I../../libltdl -I../../kdefx
> -I../../kdecore -I../../kdecore -I../../kdecore/network -I../../kdeui
> -I../../kio -I../../kio/kio -I../../kio/kfile -I../..
> -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -DQT_THREAD_SUPPORT
> -D_REENTRANT -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 ksslsettings.lo
> ksslsettings.cc
> In file included from ksslsettings.cc:47:0:
> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
> ./kopenssl.h:526:16: error: expected ';' before '(' token
> ./kopenssl.h:532:17: error: 'STACK' has not been declared
> ./kopenssl.h:538:15: error: 'STACK' has not been declared
> ./kopenssl.h:544:18: error: expected ';' before '(' token
> ./kopenssl.h:550:4: error: 'STACK' does not name a type
> ./kopenssl.h:556:16: error: 'STACK' has not been declared
> ./kopenssl.h:562:4: error: 'STACK' does not name a type
> ./kopenssl.h:828:4: error: 'STACK' does not name a type
> ./kopenssl.h:829:25: error: 'STACK' has not been declared
> ksslsettings.cc: In member function 'QString KSSLSettings::getCipherList()':
> ksslsettings.cc:157:12: error: no matching function for call to
> 'KOpenSSLProxy::sk_num(_STACK*)'
> ./kopenssl.h:538:8: note: candidate is: int KOpenSSLProxy::sk_num(int*)
> ksslsettings.cc:159:20: error: 'class KOpenSSLProxy' has no member
> named 'sk_value'
> make[5]: *** [ksslsettings.lo] Error 1
> make[5]: *** Waiting for unfinished jobs....
> In file included from kssl.cc:47:0:
> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
> ./kopenssl.h:526:16: error: expected ';' before '(' token
> ./kopenssl.h:532:17: error: 'STACK' has not been declared
> ./kopenssl.h:538:15: error: 'STACK' has not been declared
> ./kopenssl.h:544:18: error: expected ';' before '(' token
> ./kopenssl.h:550:4: error: 'STACK' does not name a type
> ./kopenssl.h:556:16: error: 'STACK' has not been declared
> ./kopenssl.h:562:4: error: 'STACK' does not name a type
> ./kopenssl.h:828:4: error: 'STACK' does not name a type
> ./kopenssl.h:829:25: error: 'STACK' has not been declared
> kssl.cc: In member function 'void KSSL::setPeerInfo()':
> kssl.cc:616:8: error: 'class KOpenSSLProxy' has no member named 'sk_dup'
> make[5]: *** [kssl.lo] Error 1
> make[5]: Leaving directory
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
> make: *** [all] Error 2
> emake failed
> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
> * died running emake, kde_src_compile:make
> *
> * Call stack:
> * ebuild.sh, line 93: Called src_compile
> * environment, line 4608: Called kde_src_compile
> * environment, line 3187: Called kde_src_compile 'all'
> * environment, line 3202: Called kde_src_compile 'make'
> * environment, line 3194: 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/kdelibs-3.5.10-r6'`,
> * the complete build log and the output of `emerge -pqv
> '=kde-base/kdelibs-3.5.10-r6'`.
> * This ebuild used the following eclasses from overlays:
> * /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/kdelibs-3.5.10-r6/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
> * Working directory:
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>
>>>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file:
>
>>>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log'
>
> * Messages for package kde-base/kdelibs-3.5.10-r6:
>
> * You have the legacyssl use flag enabled, which fixes issues with some broken
> * sites, but breaks others instead. It is strongly discouraged to use it.
> * For more information, see bug #128922.
> * On some setups, which rely on the correct update of utmp records, not using
> * utempter might not update them correctly. If you experience unexpected
> * behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled.
> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
> * died running emake, kde_src_compile:make
> *
> * Call stack:
> * ebuild.sh, line 93: Called src_compile
> * environment, line 4608: Called kde_src_compile
> * environment, line 3187: Called kde_src_compile 'all'
> * environment, line 3202: Called kde_src_compile 'make'
> * environment, line 3194: 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/kdelibs-3.5.10-r6'`,
> * the complete build log and the output of `emerge -pqv
> '=kde-base/kdelibs-3.5.10-r6'`.
> * This ebuild used the following eclasses from overlays:
> * /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/kdelibs-3.5.10-r6/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
> * Working directory:
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>
> Also, very strange thing is that the dependency tree of KDE 3 is not updated:
>
> If I have the latest openssl, which is 1.0.0j, KDE will slot-instal 0.0.8x.
>
> Is there such an incompatibility?
>
> And third issue:
>
> mDNSResponder ebuuild is not in the tree.

Was removed four months ago; this was the warning:

http://archives.gentoo.org/gentoo-dev/msg_f420c354ab23da51c943dff9cb4d9e76.xml

As the mail says, net-dns/avahi[mdnsresponder-compat] seems to cover
the same; perhaps you could use that?

> Could someone please put it back?

Unless someone steps up to maintain it (and fix all the problems it
could have), it's not going to happen.

Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


ikorot01 at gmail

Nov 20, 2012, 8:33 PM

Post #3 of 34 (2970 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Hi, Canek,
What about other 2 issues?

Thank you.


On Tue, Nov 20, 2012 at 7:12 PM, Canek Pelez Valds <caneko [at] gmail> wrote:
> On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
>> Hi, ALL,
>> I'm trying to install KDE 3 from kde-sunset overlay and am getting the
>> compiler error:
>>
>>
>> /bin/sh ../../libtool --silent --tag=CXX --mode=compile
>> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop
>> -I../../kdecore -I. -I../../kjs -I../../kdecore/network
>> -I../../kwallet/client -I../../dcop -I../../libltdl -I../../kdefx
>> -I../../kdecore -I../../kdecore -I../../kdecore/network -I../../kdeui
>> -I../../kio -I../../kio/kio -I../../kio/kfile -I../..
>> -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -DQT_THREAD_SUPPORT
>> -D_REENTRANT -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 ksslsettings.lo
>> ksslsettings.cc
>> In file included from ksslsettings.cc:47:0:
>> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
>> ./kopenssl.h:526:16: error: expected ';' before '(' token
>> ./kopenssl.h:532:17: error: 'STACK' has not been declared
>> ./kopenssl.h:538:15: error: 'STACK' has not been declared
>> ./kopenssl.h:544:18: error: expected ';' before '(' token
>> ./kopenssl.h:550:4: error: 'STACK' does not name a type
>> ./kopenssl.h:556:16: error: 'STACK' has not been declared
>> ./kopenssl.h:562:4: error: 'STACK' does not name a type
>> ./kopenssl.h:828:4: error: 'STACK' does not name a type
>> ./kopenssl.h:829:25: error: 'STACK' has not been declared
>> ksslsettings.cc: In member function 'QString KSSLSettings::getCipherList()':
>> ksslsettings.cc:157:12: error: no matching function for call to
>> 'KOpenSSLProxy::sk_num(_STACK*)'
>> ./kopenssl.h:538:8: note: candidate is: int KOpenSSLProxy::sk_num(int*)
>> ksslsettings.cc:159:20: error: 'class KOpenSSLProxy' has no member
>> named 'sk_value'
>> make[5]: *** [ksslsettings.lo] Error 1
>> make[5]: *** Waiting for unfinished jobs....
>> In file included from kssl.cc:47:0:
>> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type
>> ./kopenssl.h:526:16: error: expected ';' before '(' token
>> ./kopenssl.h:532:17: error: 'STACK' has not been declared
>> ./kopenssl.h:538:15: error: 'STACK' has not been declared
>> ./kopenssl.h:544:18: error: expected ';' before '(' token
>> ./kopenssl.h:550:4: error: 'STACK' does not name a type
>> ./kopenssl.h:556:16: error: 'STACK' has not been declared
>> ./kopenssl.h:562:4: error: 'STACK' does not name a type
>> ./kopenssl.h:828:4: error: 'STACK' does not name a type
>> ./kopenssl.h:829:25: error: 'STACK' has not been declared
>> kssl.cc: In member function 'void KSSL::setPeerInfo()':
>> kssl.cc:616:8: error: 'class KOpenSSLProxy' has no member named 'sk_dup'
>> make[5]: *** [kssl.lo] Error 1
>> make[5]: Leaving directory
>> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
>> make[4]: *** [all-recursive] Error 1
>> make[4]: Leaving directory
>> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
>> make[3]: *** [all] Error 2
>> make[3]: Leaving directory
>> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory
>> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>> make: *** [all] Error 2
>> emake failed
>> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
>> * died running emake, kde_src_compile:make
>> *
>> * Call stack:
>> * ebuild.sh, line 93: Called src_compile
>> * environment, line 4608: Called kde_src_compile
>> * environment, line 3187: Called kde_src_compile 'all'
>> * environment, line 3202: Called kde_src_compile 'make'
>> * environment, line 3194: 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/kdelibs-3.5.10-r6'`,
>> * the complete build log and the output of `emerge -pqv
>> '=kde-base/kdelibs-3.5.10-r6'`.
>> * This ebuild used the following eclasses from overlays:
>> * /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/kdelibs-3.5.10-r6/temp/build.log'.
>> * The ebuild environment file is located at
>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
>> * Working directory:
>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>>
>>>>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file:
>>
>>>>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log'
>>
>> * Messages for package kde-base/kdelibs-3.5.10-r6:
>>
>> * You have the legacyssl use flag enabled, which fixes issues with some broken
>> * sites, but breaks others instead. It is strongly discouraged to use it.
>> * For more information, see bug #128922.
>> * On some setups, which rely on the correct update of utmp records, not using
>> * utempter might not update them correctly. If you experience unexpected
>> * behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled.
>> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase):
>> * died running emake, kde_src_compile:make
>> *
>> * Call stack:
>> * ebuild.sh, line 93: Called src_compile
>> * environment, line 4608: Called kde_src_compile
>> * environment, line 3187: Called kde_src_compile 'all'
>> * environment, line 3202: Called kde_src_compile 'make'
>> * environment, line 3194: 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/kdelibs-3.5.10-r6'`,
>> * the complete build log and the output of `emerge -pqv
>> '=kde-base/kdelibs-3.5.10-r6'`.
>> * This ebuild used the following eclasses from overlays:
>> * /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/kdelibs-3.5.10-r6/temp/build.log'.
>> * The ebuild environment file is located at
>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'.
>> * Working directory:
>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10'
>>
>> Also, very strange thing is that the dependency tree of KDE 3 is not updated:
>>
>> If I have the latest openssl, which is 1.0.0j, KDE will slot-instal 0.0.8x.
>>
>> Is there such an incompatibility?
>>
>> And third issue:
>>
>> mDNSResponder ebuuild is not in the tree.
>
> Was removed four months ago; this was the warning:
>
> http://archives.gentoo.org/gentoo-dev/msg_f420c354ab23da51c943dff9cb4d9e76.xml
>
> As the mail says, net-dns/avahi[mdnsresponder-compat] seems to cover
> the same; perhaps you could use that?
>
>> Could someone please put it back?
>
> Unless someone steps up to maintain it (and fix all the problems it
> could have), it's not going to happen.
>
> Regards.
> --
> Canek Pelez Valds
> Posgrado en Ciencia e Ingeniera de la Computacin
> Universidad Nacional Autnoma de Mxico
>


purslow at ca

Nov 20, 2012, 9:48 PM

Post #4 of 34 (2967 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

121120 Canek Pelez Valds wrote:
> On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
>> I'm trying to install KDE 3 from kde-sunset overlay
>> compiler error -- snipped
>> mDNSResponder ebuild is not in the tree.

I ran into this problem & found help via the list :
have a look at the list archive for the end of October.
I got mDNSResponder from a Gentoo obsolete-pkg archive,
copied it temporarily into /usr/portage/ , enabled it in package.unmask
& got it installed successfully. After that, I removed it from Portage,
but of course the compiled files are still in my system,
so the rest of KDE 3 which I use ( 3 pkgs only) work.
The correct way to deal with such a dep is via a Portage local overlay.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca


rdalek1967 at gmail

Nov 20, 2012, 9:57 PM

Post #5 of 34 (2966 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Philip Webb wrote:
> 121120 Canek Pelez Valds wrote:
>> On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
>>> I'm trying to install KDE 3 from kde-sunset overlay
>>> compiler error -- snipped
>>> mDNSResponder ebuild is not in the tree.
> I ran into this problem & found help via the list :
> have a look at the list archive for the end of October.
> I got mDNSResponder from a Gentoo obsolete-pkg archive,
> copied it temporarily into /usr/portage/ , enabled it in package.unmask
> & got it installed successfully. After that, I removed it from Portage,
> but of course the compiled files are still in my system,
> so the rest of KDE 3 which I use ( 3 pkgs only) work.
> The correct way to deal with such a dep is via a Portage local overlay.
>


I'm going to post what is really several messages. I have this stored
locally so it is easier to search for things than on the web. Here is
the exchange between a few folks on this:

> E. Liddell wrote:
>> On Tue, 30 Oct 2012 08:06:03 -0400
>> Philip Webb <purslow [at] ca> wrote:
>>
>>> 121029 E. Liddell wrote:
>>>> The following USE flags allow kdelibs to compile successfully for me:
>>>> [ebuild R ~] kde-base/kdelibs-3.5.10-r10::kde-sunset USE="acl alsa branding jpeg2k spell tiff -arts -avahi -bindist -cups -debug -doc -fam -kdehiddenvisibility -kerberos -legacyssl -lua -openexr -utempter"
>>> What I get is :
>>>
>>> root:519 ~> USE="acl alsa branding jpeg2k spell tiff -arts -avahi -bindist -cups -debug -doc -fam -kdehiddenvisibility -kerberos -legacyssl -lua -openexr -utempter" emerge -pv =kde-base/kdelibs-3.5.10-r10
>>>
>>> These are the packages that would be merged, in order:
>>> Calculating dependencies... done!
>>>
>>> emerge: there are no ebuilds to satisfy "net-misc/mDNSResponder".
>>> (dependency required by "kde-base/kdelibs-3.5.10-r10[-bindist,-avahi]" [ebuild])
>>> (dependency required by "=kde-base/kdelibs-3.5.10-r10" [argument])
>>>
>>> How do you manage to get away with "-avahi" ?
>> A-*ha*.
>>
>> It looks like mDNSResponder was lastrited out of the main Portage tree only
>> three months ago. Presumably I "got away" with -avahi because I had
>> mDNSResponder installed previous to its removal from the Portage tree,
>> so it exists on my system as a sort of phantom (Portage knows it's installed
>> and can link stuff to it, but there's no associated ebuild).
>>
>> mDNSResponder ebuilds should be obtainable from
>> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/mDNSResponder/?hideattic=0
>>
>> As the changelog indicates that the last tweak to this package was ~6 months
>> ago, I would expect it to still compile.
>>
>> If anyone from kde-sunset is still reading this thread, I would suggest adopting
>> this package into the overlay.
>>
>>

That should help. If you want to do a local overlay, just check out the
guide on Gentoo.org or the wiki. It's not hard and last I looked, they
give step by step instructions.

Hope that helps.

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!


ikorot01 at gmail

Nov 20, 2012, 10:52 PM

Post #6 of 34 (2961 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Guys,
Does this mean that the errors I'm seeing are from missing mDNSResponder?

Thank you.



On Tue, Nov 20, 2012 at 9:57 PM, Dale <rdalek1967 [at] gmail> wrote:
> Philip Webb wrote:
>> 121120 Canek Pelez Valds wrote:
>>> On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
>>>> I'm trying to install KDE 3 from kde-sunset overlay
>>>> compiler error -- snipped
>>>> mDNSResponder ebuild is not in the tree.
>> I ran into this problem & found help via the list :
>> have a look at the list archive for the end of October.
>> I got mDNSResponder from a Gentoo obsolete-pkg archive,
>> copied it temporarily into /usr/portage/ , enabled it in package.unmask
>> & got it installed successfully. After that, I removed it from Portage,
>> but of course the compiled files are still in my system,
>> so the rest of KDE 3 which I use ( 3 pkgs only) work.
>> The correct way to deal with such a dep is via a Portage local overlay.
>>
>
>
> I'm going to post what is really several messages. I have this stored
> locally so it is easier to search for things than on the web. Here is
> the exchange between a few folks on this:
>
>> E. Liddell wrote:
>>> On Tue, 30 Oct 2012 08:06:03 -0400
>>> Philip Webb <purslow [at] ca> wrote:
>>>
>>>> 121029 E. Liddell wrote:
>>>>> The following USE flags allow kdelibs to compile successfully for me:
>>>>> [ebuild R ~] kde-base/kdelibs-3.5.10-r10::kde-sunset USE="acl alsa branding jpeg2k spell tiff -arts -avahi -bindist -cups -debug -doc -fam -kdehiddenvisibility -kerberos -legacyssl -lua -openexr -utempter"
>>>> What I get is :
>>>>
>>>> root:519 ~> USE="acl alsa branding jpeg2k spell tiff -arts -avahi -bindist -cups -debug -doc -fam -kdehiddenvisibility -kerberos -legacyssl -lua -openexr -utempter" emerge -pv =kde-base/kdelibs-3.5.10-r10
>>>>
>>>> These are the packages that would be merged, in order:
>>>> Calculating dependencies... done!
>>>>
>>>> emerge: there are no ebuilds to satisfy "net-misc/mDNSResponder".
>>>> (dependency required by "kde-base/kdelibs-3.5.10-r10[-bindist,-avahi]" [ebuild])
>>>> (dependency required by "=kde-base/kdelibs-3.5.10-r10" [argument])
>>>>
>>>> How do you manage to get away with "-avahi" ?
>>> A-*ha*.
>>>
>>> It looks like mDNSResponder was lastrited out of the main Portage tree only
>>> three months ago. Presumably I "got away" with -avahi because I had
>>> mDNSResponder installed previous to its removal from the Portage tree,
>>> so it exists on my system as a sort of phantom (Portage knows it's installed
>>> and can link stuff to it, but there's no associated ebuild).
>>>
>>> mDNSResponder ebuilds should be obtainable from
>>> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/mDNSResponder/?hideattic=0
>>>
>>> As the changelog indicates that the last tweak to this package was ~6 months
>>> ago, I would expect it to still compile.
>>>
>>> If anyone from kde-sunset is still reading this thread, I would suggest adopting
>>> this package into the overlay.
>>>
>>>
>
> That should help. If you want to do a local overlay, just check out the
> guide on Gentoo.org or the wiki. It's not hard and last I looked, they
> give step by step instructions.
>
> Hope that helps.
>
> Dale
>
> :-) :-)
>
> --
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
>
>


ejlddll at googlemail

Nov 21, 2012, 3:34 AM

Post #7 of 34 (2964 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, 20 Nov 2012 22:52:58 -0800
Igor Korot <ikorot01 [at] gmail> wrote:

> Guys,
> Does this mean that the errors I'm seeing are from missing mDNSResponder?

You need to do three things, as far as I can tell: get the mDNSResponder ebuild
on your system, pass the USE flag -avahi, and unmask kdelibs-3.5.10-r10,
which is patched for more recent libraries (including >=openssl-1.0.0).


fatzer2 at gmail

Nov 21, 2012, 3:38 AM

Post #8 of 34 (2958 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

2012/11/21 Igor Korot <ikorot01 [at] gmail>:
> Guys,
> Does this mean that the errors I'm seeing are from missing mDNSResponder?
>
> Thank you.
>
Nope, this is openssl stuff AFAIR it was fixed in newer revisions.
Just unmask kde-base/kdelibs-3.5.10-r10 it should compile well.


brent at keycorner

Nov 21, 2012, 10:58 AM

Post #9 of 34 (2959 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, 20 Nov 2012, Canek Pel?ez Vald?s wrote:

> On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
[...]
>> Also, very strange thing is that the dependency tree of KDE 3 is not updated:
>>
>> If I have the latest openssl, which is 1.0.0j, KDE will slot-instal 0.0.8x.
>>
>> Is there such an incompatibility?

You can use the newest OpenSSL. The only problem is that sftp:// URL
support in programs like Konqueror will no longer work, because
apparently the kioslaves don't know how to talk to the new SSH. I've
been able to live without that though by using FUSE mounts. There's no
reason to keep an old OpenSSL around, and in fact, it's insecure.


>> And third issue:
>>
>> mDNSResponder ebuuild is not in the tree.
>
> Was removed four months ago; this was the warning:
>
> http://archives.gentoo.org/gentoo-dev/msg_f420c354ab23da51c943dff9cb4d9e76.xml
>
> As the mail says, net-dns/avahi[mdnsresponder-compat] seems to cover
> the same; perhaps you could use that?
>
>> Could someone please put it back?
>
> Unless someone steps up to maintain it (and fix all the problems it
> could have), it's not going to happen.

The solution I'm using here (since I really don't want or need either
one of them) is that I've setup only the KDE packages that require it to
build with the avahi USE flag, and nothing else anywhere. It is also
necessary to put in a mask against gentoo's main repository Avahi, and
unmask the latest version of kde-sunset's Avahi. The results of a grep
through my /etc/portage for 'avahi' shows what I mean:

/etc/portage/package.use:kde-base/kdelibs arts avahi
/etc/portage/package.keywords:net-dns/avahi::kde-sunset ~amd64
/etc/portage/package.mask:net-dns/avahi::gentoo


The one other bit of help I might offer with kde-sunset is that I've
found that if something doesn't build correctly, there is very often a
masked patched version in the overlay that fixes the problem that will
only become available if you keyword it. All sorts of things can be
fixed with an "~amd64" on the package that's having trouble.

--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky


serghei at thel

Nov 21, 2012, 11:07 AM

Post #10 of 34 (2956 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Wednesday 21 November 2012 20:58:08 Brent Busby wrote:
> On Tue, 20 Nov 2012, Canek Pel?ez Vald?s wrote:
> > On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01 [at] gmail> wrote:
>
> [...]
>
> >> Also, very strange thing is that the dependency tree of KDE 3 is not
> >> updated:
> >>
> >> If I have the latest openssl, which is 1.0.0j, KDE will slot-instal
> >> 0.0.8x.
> >>
> >> Is there such an incompatibility?
>
> You can use the newest OpenSSL. The only problem is that sftp:// URL
> support in programs like Konqueror will no longer work, because
> apparently the kioslaves don't know how to talk to the new SSH. I've
> been able to live without that though by using FUSE mounts. There's no
> reason to keep an old OpenSSL around, and in fact, it's insecure.

Seems that kde-sunset overlay is not very well maintained :)
The sftp kioslave was fixed long time ago:

https://github.com/serghei/kde3-kdebase/commit/c12ee4b501e4a44dd8c52b9b8e0ddbe875afb466

[...]

--
Serghei


brent at keycorner

Nov 21, 2012, 1:10 PM

Post #11 of 34 (2955 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Wed, 21 Nov 2012, Serghei Amelian wrote:

> Seems that kde-sunset overlay is not very well maintained :)
> The sftp kioslave was fixed long time ago:
>
> https://github.com/serghei/kde3-kdebase/commit/c12ee4b501e4a44dd8c52b9b8e0ddbe875afb466

That would be nice to have in the overlay... It's nice for editing web
sites in Quanta to not have to start a FUSE mount first.

--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky


ikorot01 at gmail

Nov 21, 2012, 2:40 PM

Post #12 of 34 (2960 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Where can I get it?
I already have layman installed, so it just a matter of getting proper
overlay...

Thank you.

On Wed, Nov 21, 2012 at 3:34 AM, E. Liddell <ejlddll [at] googlemail> wrote:
> On Tue, 20 Nov 2012 22:52:58 -0800
> Igor Korot <ikorot01 [at] gmail> wrote:
>
>> Guys,
>> Does this mean that the errors I'm seeing are from missing mDNSResponder?
>
> You need to do three things, as far as I can tell: get the mDNSResponder ebuild
> on your system, pass the USE flag -avahi, and unmask kdelibs-3.5.10-r10,
> which is patched for more recent libraries (including >=openssl-1.0.0).
>


ejlddll at googlemail

Nov 21, 2012, 7:21 PM

Post #13 of 34 (2954 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Wed, 21 Nov 2012 14:40:05 -0800
Igor Korot <ikorot01 [at] gmail> wrote:

> Where can I get it?
> I already have layman installed, so it just a matter of getting proper
> overlay...

There is no formal overlay. You can obtain the ebuild from the following URL,
already posted in an earlier reply:

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/mDNSResponder/?hideattic=0


ikorot01 at gmail

Nov 26, 2012, 12:50 PM

Post #14 of 34 (2947 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Hi, guys,
I got mDNSResponder and restarted emerge.
It went OK for some time and then stopped with following:

* Messages for package kde-base/ksvg-3.5.10:

* ERROR: kde-base/ksvg-3.5.10 failed (install phase):
* emake install failed.
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 4690: Called kde-meta_src_install
* environment, line 3116: Called kde-meta_src_install 'make' 'dodoc'
* environment, line 3125: Called die
* The specific snippet of code:
* emake DESTDIR="${D}" destdir="${D}"
install || die "emake install failed.";
*
* If you need support, post the output of `emerge --info
'=kde-base/ksvg-3.5.10'`,
* the complete build log and the output of `emerge -pqv
'=kde-base/ksvg-3.5.10'`.
* 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/ksvg-3.5.10/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/kde-base/ksvg-3.5.10/temp/environment'.
* Working directory:
'/var/tmp/portage/kde-base/ksvg-3.5.10/work/ksvg-3.5.10/ksvg'
* S: '/var/tmp/portage/kde-base/ksvg-3.5.10/work/ksvg-3.5.10'

* GNU info directory index is up-to-date.

* IMPORTANT: 3 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.


Any idea what is going on? Is there a later revision I need to unmask?

Thank you.

On Wed, Nov 21, 2012 at 7:21 PM, E. Liddell <ejlddll [at] googlemail> wrote:
> On Wed, 21 Nov 2012 14:40:05 -0800
> Igor Korot <ikorot01 [at] gmail> wrote:
>
>> Where can I get it?
>> I already have layman installed, so it just a matter of getting proper
>> overlay...
>
> There is no formal overlay. You can obtain the ebuild from the following URL,
> already posted in an earlier reply:
>
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/mDNSResponder/?hideattic=0
>


1i5t5.duncan at cox

Nov 26, 2012, 2:14 PM

Post #15 of 34 (2936 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Igor Korot posted on Mon, 26 Nov 2012 12:50:34 -0800 as excerpted:

> Hi, guys,
> I got mDNSResponder and restarted emerge.
> It went OK for some time and then stopped with following:
>
> * Messages for package kde-base/ksvg-3.5.10:
>
> * ERROR: kde-base/ksvg-3.5.10 failed (install phase):
> * emake install failed.

OK, you got thru the build phase, but kde3 used to (for me, it's used to,
I've been on kde4 since before kde3 got "sunset") do an awful lot in the
install phase as well, and that's what's screwing up. (Note that the
"install phase" is still the "fake install", to the location under
$PORTAGE_TMPDIR, the real install is called qmerge, and simply copies
everything from the fake install under $PORTAGE_TMPDIR to the live
system.)

But....

> * The specific snippet of code:
> * emake DESTDIR="${D}" destdir="${D}" install || \
> * die "emake install failed.";

> * The complete build log is located at
> '/var/tmp/portage/kde-base/ksvg-3.5.10/temp/build.log'.

... you included the portage error, but not the make install
log with its error... and you didn't include an emerge --verbose
--pretend or similar, to see the USE flags it used, either!

The easiest way to find the first error is often to either grep for or
open the log file in your favorite editor and search for, "error". With
a lot of packages the first few hits will be on errorlog or whatever
modules, but then you'll start hitting the errors that triggered the
die. You'll want to post at least the code surrounding the first one.
(I usually backup from there until I find the "entering whatever-subdir"
line before the error, and post from there thru the "leaving whatever
subdir" line after the error, when I bug-file, then attach the whole
build-log as well, just in case it's needed.)


> * IMPORTANT: 3 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.

Unlikely to be apropos here, but you let news items build up without
reading them? You /do/ realize that's a good way to get an unbootable
system or the like, because you failed to follow the instructions in the
news items and thus didn't do the necessary updates that they warned you
about, right?

Ideally, you read news items right away, before emerging anything (at
least once eselect itself is merged), just as you always either to an
emerge --pretend --verbose first or use emerge --ask, to see what it's
going to do and check its sanity (plus look for any USE flag changes and/
or what the flags are on new packages, making changes as necessary),
before actually letting portage do it.

Similarly, after you're done with your updates, it's always a good idea
to run revdep-rebuild, etc-update (or the like), and emerge --depclean
(don't forget the --ask/--pretend first!), to keep the cruft to a minimum.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman


ejlddll at googlemail

Nov 26, 2012, 2:18 PM

Post #16 of 34 (2939 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Mon, 26 Nov 2012 12:50:34 -0800
Igor Korot <ikorot01 [at] gmail> wrote:

> Hi, guys,
> I got mDNSResponder and restarted emerge.
> It went OK for some time and then stopped with following:
>
> * Messages for package kde-base/ksvg-3.5.10:
[snip]
> Any idea what is going on? Is there a later revision I need to unmask?

There's an -r1:

# ls /var/lib/layman/kde-sunset/kde-base/ksvg/
ChangeLog files ksvg-3.5.10.ebuild ksvg-3.5.10-r1.ebuild Manifest metadata.xml

No idea if it resolves your issue, though. I'd suggest passing --keep-going to emerge
and dealing with all the borked packages at the end (if you're trying to emerge KDE3
using stable packages, there may be quite a few . . .)


ikorot01 at gmail

Nov 26, 2012, 4:34 PM

Post #17 of 34 (2935 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

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:
*
* (kde-base/ksvg-3.5.10::kde-sunset, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/kde-base/ksvg-3.5.10/temp/build.log'
* (kde-base/kdegraphics-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/kde-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/kopete-3.5.10-r5::kde-sunset, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/kde-base/kopete-3.5.10-r5/temp/build.log'
* (kde-base/kdenetwork-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/kate-plugins-3.5.10::kde-sunset, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/kde-base/kate-plugins-3.5.10/temp/build.log'
* (kde-base/kdeaddons-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/konsolekalendar-3.5.10::kde-sunset, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/kde-base/konsolekalendar-3.5.10/temp/build.log'
* (kde-base/kdepim-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/korganizer-3.5.10::kde-sunset, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/kde-base/korganizer-3.5.10/temp/build.log'
* (kde-base/kontact-specialdates-3.5.10::kde-sunset, ebuild
scheduled for merge)
* (kde-base/kcontrol-3.5.10::kde-sunset, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/kde-base/kcontrol-3.5.10/temp/build.log'
* (kde-base/kdm-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/konqueror-akregator-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/kmail-3.5.10::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)
* (kde-base/kdebase-meta-3.5.10::kde-sunset, ebuild scheduled for merge)
* (kde-base/konq-plugins-3.5.10::kde-sunset, ebuild scheduled for merge)
*

What would be the first package to look at? (meaning most important one?)

Thank you.


On Mon, Nov 26, 2012 at 2:18 PM, E. Liddell <ejlddll [at] googlemail> wrote:
> On Mon, 26 Nov 2012 12:50:34 -0800
> Igor Korot <ikorot01 [at] gmail> wrote:
>
>> Hi, guys,
>> I got mDNSResponder and restarted emerge.
>> It went OK for some time and then stopped with following:
>>
>> * Messages for package kde-base/ksvg-3.5.10:
> [snip]
>> Any idea what is going on? Is there a later revision I need to unmask?
>
> There's an -r1:
>
> # ls /var/lib/layman/kde-sunset/kde-base/ksvg/
> ChangeLog files ksvg-3.5.10.ebuild ksvg-3.5.10-r1.ebuild Manifest metadata.xml
>
> No idea if it resolves your issue, though. I'd suggest passing --keep-going to emerge
> and dealing with all the borked packages at the end (if you're trying to emerge KDE3
> using stable packages, there may be quite a few . . .)
>


ikorot01 at gmail

Nov 26, 2012, 4:49 PM

Post #18 of 34 (2972 views)
Permalink
Re: Re: Dependencies of KDE 3 [In reply to]

Hi, Duncan,

On Mon, Nov 26, 2012 at 2:14 PM, Duncan <1i5t5.duncan [at] cox> wrote:
> Igor Korot posted on Mon, 26 Nov 2012 12:50:34 -0800 as excerpted:
>
>> Hi, guys,
>> I got mDNSResponder and restarted emerge.
>> It went OK for some time and then stopped with following:
>>
>> * Messages for package kde-base/ksvg-3.5.10:
>>
>> * ERROR: kde-base/ksvg-3.5.10 failed (install phase):
>> * emake install failed.
>
> OK, you got thru the build phase, but kde3 used to (for me, it's used to,
> I've been on kde4 since before kde3 got "sunset") do an awful lot in the
> install phase as well, and that's what's screwing up. (Note that the
> "install phase" is still the "fake install", to the location under
> $PORTAGE_TMPDIR, the real install is called qmerge, and simply copies
> everything from the fake install under $PORTAGE_TMPDIR to the live
> system.)
>
> But....
>
>> * The specific snippet of code:
>> * emake DESTDIR="${D}" destdir="${D}" install || \
>> * die "emake install failed.";
>
>> * The complete build log is located at
>> '/var/tmp/portage/kde-base/ksvg-3.5.10/temp/build.log'.
>
> ... you included the portage error, but not the make install
> log with its error... and you didn't include an emerge --verbose
> --pretend or similar, to see the USE flags it used, either!

LearningRight samples # emerge --info
Portage 2.1.11.31 (default/linux/amd64/10.0/desktop/gnome, gcc-4.5.3,
glibc-2.14.1-r3, 3.4.9-gentoo x86_64)
=================================================================
System uname: Linux-3.4.9-gentoo-x86_64-Intel-R-_Core-TM-2_Duo_CPU_E6750_ [at] _2
Timestamp of tree: Fri, 16 Nov 2012 20:00:01 +0000
ld GNU ld (GNU Binutils) 2.21.1
app-shells/bash: 4.2_p20
dev-lang/python: 2.6.8, 2.7.3-r2, 3.2.3
dev-util/cmake: 2.8.8-r3
dev-util/pkgconfig: 0.27.1
sys-apps/baselayout: 2.1-r1
sys-apps/openrc: 0.9.8.4
sys-apps/sandbox: 2.5
sys-devel/autoconf: 2.13, 2.68
sys-devel/automake: 1.9.6-r3, 1.10.3, 1.11.6
sys-devel/binutils: 2.21.1-r1
sys-devel/gcc: 4.5.3-r2
sys-devel/gcc-config: 1.6
sys-devel/libtool: 2.4-r1
sys-devel/make: 3.82-r1
sys-kernel/linux-headers: 3.1 (virtual/os-headers)
sys-libs/glibc: 2.14.1-r3
Repositories: gentoo kde-sunset
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* - [at] EUL AdobeFlash-10.3"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=core2 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/config
/usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
/etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.4/ext-active/
/etc/php/cli-php5.4/ext-active/ /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=core2 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified
distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch
protect-owned sandbox sfperms strict unknown-features-warn
unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://gentoo.osuosl.org/"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --stats --human-readable
--timeout=180 --exclude=/distfiles --exclude=/local
--exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/var/lib/layman/kde-sunset"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2
cairo cdda cdr cli colord consolekit cracklib crypt cxx dbus dri dts
dvd dvdr eds emboss encode evo exif fam firefox flac fortran gdbm gif
gnome gnome-keyring gnome-online-accounts gpm gstreamer gtk iconv ipv6
jpeg lcms ldap libnotify mad midi mmx mng modules mp3 mp4 mpeg mudflap
multilib nautilus ncurses nls nptl ogg opengl openmp pam pango pcre
pdf png policykit ppds pppd pulseaudio qt3support qt4 readline sdl
session socialweb spell sse sse2 ssl startup-notification svg tcpd
tiff truetype udev udisks unicode upower usb vorbis wxwidgets x264 xcb
xml xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem
bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801
hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx
via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix
dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat
linear meter mmap_emul mulaw multi null plug rate route share shm
softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd
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 cgi cgid 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" CALLIGRA_FEATURES="kexi words flow plan sheets
stage tables krita karbon braindump" CAMERAS="ptp2"
COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog"
ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18
garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver
oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip
tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb
ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console
presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_TARGETS="python2_7
python3_2" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU"
VIDEO_CARDS="radeon" XTABLES_ADDONS="quota2 psd pknock lscan length2
ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq
steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG,
LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS,
PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

LearningRight samples # emerge -pv ksvg

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild N ~] kde-base/ksvg-3.5.10-r1:3.5::kde-sunset USE="-debug" 0 kB

Total: 1 package (1 new), Size of downloads: 0 kB

>
> The easiest way to find the first error is often to either grep for or
> open the log file in your favorite editor and search for, "error". With
> a lot of packages the first few hits will be on errorlog or whatever
> modules, but then you'll start hitting the errors that triggered the
> die. You'll want to post at least the code surrounding the first one.
> (I usually backup from there until I find the "entering whatever-subdir"
> line before the error, and post from there thru the "leaving whatever
> subdir" line after the error, when I bug-file, then attach the whole
> build-log as well, just in case it's needed.)

And here is the error from the build.log:

/bin/sh ../../../../libtool --silent --tag=CC --mode=link
x86_64-pc-linux-gnu-gcc -std=iso9899:1990 -W -Wall -Wchar-subscripts
-Wshadow -Wpointer-arith -Wm$
make[4]: Entering directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/art_support'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/art_support'
make[3]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/art_support'
Making install in libtext2path
make[3]: Entering directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/libtext2path'
Making install in src
make[4]: Entering directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/libtext2path/src'
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
/bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
-I/usr/include/freetype2 $
In file included from /usr/include/fribidi/fribidi.h:35:0,
from Converter.cpp:25:
/usr/include/fribidi/fribidi-common.h:65:20: fatal error: glib.h: No
such file or directory
compilation terminated.
make[4]: *** [Converter.lo] Error 1
make[4]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/libtext2path/src'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs/libtext2path'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/libs'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl'
make: *** [install-recursive] Error 1

It references "glib.h", but I don't understand this at all.
Does this mean that this package depends on the GTK+? Or "g" in the
"glib.h" means something else?

I am under GNOME2 stable with GTK+2, BTW...

>
>
>> * IMPORTANT: 3 news items need reading for repository 'gentoo'.
>> * Use eselect news to read news items.
>
> Unlikely to be apropos here, but you let news items build up without
> reading them? You /do/ realize that's a good way to get an unbootable
> system or the like, because you failed to follow the instructions in the
> news items and thus didn't do the necessary updates that they warned you
> about, right?
>
> Ideally, you read news items right away, before emerging anything (at
> least once eselect itself is merged), just as you always either to an
> emerge --pretend --verbose first or use emerge --ask, to see what it's
> going to do and check its sanity (plus look for any USE flag changes and/
> or what the flags are on new packages, making changes as necessary),
> before actually letting portage do it.
>
> Similarly, after you're done with your updates, it's always a good idea
> to run revdep-rebuild, etc-update (or the like), and emerge --depclean
> (don't forget the --ask/--pretend first!), to keep the cruft to a minimum.

Well, this is not an issue here, AFAICT. ;-)

Thank you.

>
> --
> Duncan - List replies preferred. No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." Richard Stallman
>
>


1i5t5.duncan at cox

Nov 26, 2012, 9:34 PM

Post #19 of 34 (2946 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Igor Korot posted on Mon, 26 Nov 2012 16:49:01 -0800 as excerpted:

>> ... you included the portage error, but not the make install log with
>> its error... and you didn't include an emerge --verbose --pretend or
>> similar, to see the USE flags it used, either!

> LearningRight samples # emerge -pv ksvg
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild N ~] kde-base/ksvg-3.5.10-r1:3.5::kde-sunset USE="-debug" 0
> kB

OK, so no real USE flags to worry about. (People still running kde3
would likely know that, but I didn't, because as I said I've long been on
kde4.) Knowing there's no USE flags to speak of means the error isn't
something that could be worked around by simply flipping a USE flag, a
useful trick to keep in mind for those times when the problem does look
like it might be USE flag related, especially if you don't really care
which way you go with that particular flag.



>> The easiest way to find the first error is often to either grep for or
>> open the log file in your favorite editor and search for, "error".
>> With a lot of packages the first few hits will be on errorlog or
>> whatever modules, but then you'll start hitting the errors that
>> triggered the die. You'll want to post at least the code surrounding
>> the first one. (I usually backup from there until I find the "entering
>> whatever-subdir"
>> line before the error, and post from there thru the "leaving whatever
>> subdir" line after the error, when I bug-file, then attach the whole
>> build-log as well, just in case it's needed.)
>
> And here is the error from the build.log:

> Making install in src make[4]: Entering directory
> `/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/
libs/libtext2path/src'
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> /bin/sh ../../../../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../../..
> -I/usr/include/freetype2 $
> In file included from /usr/include/fribidi/fribidi.h:35:0,
> from Converter.cpp:25:
> /usr/include/fribidi/fribidi-common.h:65:20: fatal error: glib.h: No
> such file or directory compilation terminated.
> make[4]: *** [Converter.lo] Error 1 make[4]: Leaving directory
> `/var/tmp/portage/kde-base/ksvg-3.5.10-r1/work/ksvg-3.5.10/ksvg/impl/
libs/libtext2path/src'

> It references "glib.h", but I don't understand this at all.
> Does this mean that this package depends on the GTK+? Or "g" in the
> "glib.h" means something else?
>
> I am under GNOME2 stable with GTK+2, BTW...

glib was originally part of the gtk+ core indeed, and remains hosted at
gtk.org. However, now days it's an extremely widely used base dependency
required by pretty much any X-based app that's anywhere close to modern,
including much or all of kde (I'm not sure if it's a dep of kdelibs or
not), and is thus no longer really part of gtk per se but rather, now
more like a general purpose library required by nearly anything X-based
that's even close to modern, including much of kde (even kde3), as I said.

Note that the problem traces thru the fribidi (bi-dir text utilities
helper lib, for right-to-left as well as left-to-right text, etc, it's
part of the i18n (i-18-letters-n, internationalization) stuff) header
files.

Thus, remerging your fribidi package may eliminate the problem... or
trace the root of the problem to a fribidi (or glib) issue if /fribidi/
fails to build with a similar glib.h header-file error. Or it may not,
but if all it takes is a fribidi rebuild (or even a glib rebuild, then a
fribidi rebuild, then back to ksvg), it's a simple enough fix, and the
problem would surely eventually spread if you didn't fix it too, given
the number of packages that require glib and/or fribidi.

That's why the first real error is so important to post (and why I asked
for it). With what you originally posted there was no way on earth to
trace the problem back to fribidi or glib. Knowing what that first error
is can make all the difference in the world!

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman


ejlddll at googlemail

Nov 27, 2012, 3:51 AM

Post #20 of 34 (2934 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Mon, 26 Nov 2012 16:34:33 -0800
Igor Korot <ikorot01 [at] gmail> 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?)

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:

> * (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.

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:

# equery meta kcontrol
* kde-base/kcontrol [gentoo]
Herd: kde (kde [at] gentoo)
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.


ikorot01 at gmail

Nov 27, 2012, 11:21 AM

Post #21 of 34 (2936 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

Hi,

On Tue, Nov 27, 2012 at 3:51 AM, E. Liddell <ejlddll [at] googlemail> wrote:
> On Mon, 26 Nov 2012 16:34:33 -0800
> Igor Korot <ikorot01 [at] gmail> 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 [at] gentoo)
> 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.
>


ikorot01 at gmail

Nov 27, 2012, 11:27 AM

Post #22 of 34 (2934 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, Nov 27, 2012 at 11:21 AM, Igor Korot <ikorot01 [at] gmail> wrote:
> Hi,
>
> On Tue, Nov 27, 2012 at 3:51 AM, E. Liddell <ejlddll [at] googlemail> wrote:
>> On Mon, 26 Nov 2012 16:34:33 -0800
>> Igor Korot <ikorot01 [at] gmail> 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?

The same error goes to konsolekalendar...

>
> 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 [at] gentoo)
>> 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.
>>


ikorot01 at gmail

Nov 27, 2012, 11:32 AM

Post #23 of 34 (2937 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, Nov 27, 2012 at 11:27 AM, Igor Korot <ikorot01 [at] gmail> wrote:
> On Tue, Nov 27, 2012 at 11:21 AM, Igor Korot <ikorot01 [at] gmail> wrote:
>> Hi,
>>
>> On Tue, Nov 27, 2012 at 3:51 AM, E. Liddell <ejlddll [at] googlemail> wrote:
>>> On Mon, 26 Nov 2012 16:34:33 -0800
>>> Igor Korot <ikorot01 [at] gmail> 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?
>
> The same error goes to konsolekalendar...
>
>>
>> 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 [at] gentoo)
>>> 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.

kate-plugins also fail to compile:

LearningRight temp # equery meta kate-plugins
* kde-base/kate-plugins [kde-sunset]
Herd: kde (kde [at] gentoo)
Maintainer: None specified
Upstream: None specified
Homepage: http://www.kde.org/
Location: /var/lib/layman/kde-sunset/kde-base/kate-plugins
Keywords: 3.5.10:3.5: alpha amd64 hppa ia64 ppc ppc64 sparc x86

/bin/sh ../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../..
-I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT
-D_REENTRANT -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
plugin_katetabbarextension.lo plugin_katetabbarextension.cpp
In file included from plugin_katetabbarextension.cpp:27:0:
plugin_katetabbarextension.h: In constructor 'MyPtrList::MyPtrList()':
plugin_katetabbarextension.h:56:54: error: cannot call constructor
'MyPtrList::QPtrList' directly
plugin_katetabbarextension.h:56:54: error: for a function-style
cast, remove the redundant '::QPtrList'
plugin_katetabbarextension.h: At global scope:
plugin_katetabbarextension.h:309:13: warning: unused parameter 'number'
plugin_katetabbarextension.h:309:13: warning: unused parameter 'size'
make[3]: *** [plugin_katetabbarextension.lo] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10/kate/tabbarextension'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10/kate'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10'
make: *** [all] Error 2
emake failed


>>>
>>> Oh, and incidentally,
>>>
>>> No.
>>>>Should I top-post?
>>>
>>> Good luck.
>>>


ikorot01 at gmail

Nov 27, 2012, 11:43 AM

Post #24 of 34 (2937 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

On Tue, Nov 27, 2012 at 11:32 AM, Igor Korot <ikorot01 [at] gmail> wrote:
> On Tue, Nov 27, 2012 at 11:27 AM, Igor Korot <ikorot01 [at] gmail> wrote:
>> On Tue, Nov 27, 2012 at 11:21 AM, Igor Korot <ikorot01 [at] gmail> wrote:
>>> Hi,
>>>
>>> On Tue, Nov 27, 2012 at 3:51 AM, E. Liddell <ejlddll [at] googlemail> wrote:
>>>> On Mon, 26 Nov 2012 16:34:33 -0800
>>>> Igor Korot <ikorot01 [at] gmail> 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?
>>
>> The same error goes to konsolekalendar...
>>
>>>
>>> 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 [at] gentoo)
>>>> 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.
>
> kate-plugins also fail to compile:
>
> LearningRight temp # equery meta kate-plugins
> * kde-base/kate-plugins [kde-sunset]
> Herd: kde (kde [at] gentoo)
> Maintainer: None specified
> Upstream: None specified
> Homepage: http://www.kde.org/
> Location: /var/lib/layman/kde-sunset/kde-base/kate-plugins
> Keywords: 3.5.10:3.5: alpha amd64 hppa ia64 ppc ppc64 sparc x86
>
> /bin/sh ../../libtool --silent --tag=CXX --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../..
> -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT
> -D_REENTRANT -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
> plugin_katetabbarextension.lo plugin_katetabbarextension.cpp
> In file included from plugin_katetabbarextension.cpp:27:0:
> plugin_katetabbarextension.h: In constructor 'MyPtrList::MyPtrList()':
> plugin_katetabbarextension.h:56:54: error: cannot call constructor
> 'MyPtrList::QPtrList' directly
> plugin_katetabbarextension.h:56:54: error: for a function-style
> cast, remove the redundant '::QPtrList'
> plugin_katetabbarextension.h: At global scope:
> plugin_katetabbarextension.h:309:13: warning: unused parameter 'number'
> plugin_katetabbarextension.h:309:13: warning: unused parameter 'size'
> make[3]: *** [plugin_katetabbarextension.lo] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10/kate/tabbarextension'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10/kate'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/kde-base/kate-plugins-3.5.10/work/kate-plugins-3.5.10'
> make: *** [all] Error 2
> emake failed

Finally latest kopete fails qwith following:

/bin/sh ../../../libtool --silent --tag=CXX --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../..
-I../../../kopete/protocols/gadu/libgadu -I/usr/kde/3.5/include
-I/usr/qt/3/include -I. -DKDE_NO_COMPAT -DQT_NO_COMPAT
-DQT_NO_CAST_ASCII -DQT_NO_ASCII_CAST -I../../../kopete/libkopete
-I../../../kopete/libkopete -I../../../kopete/libkopete/avdevice
-I../../../kopete/libkopete/ui -I../../../kopete/libkopete/ui
-I../../../kopete/libkopete/private -I../../../kopete/libkopete/ui
-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 videodevicepool.lo videodevicepool.cpp
In file included from videodevice.cpp:27:0:
videodevice.h:55:28: fatal error: linux/videodev.h: No such file or directory
compilation terminated.
make[4]: *** [videodevice.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
In file included from videodevicepool.cpp:29:0:
videodevice.h:55:28: fatal error: linux/videodev.h: No such file or directory
compilation terminated.
make[4]: *** [videodevicepool.lo] Error 1
make[4]: Leaving directory
`/var/tmp/portage/kde-base/kopete-3.5.10-r6/work/kopete-3.5.10/kopete/libkopete/avdevice'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/kde-base/kopete-3.5.10-r6/work/kopete-3.5.10/kopete/libkopete'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kde-base/kopete-3.5.10-r6/work/kopete-3.5.10/kopete'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kde-base/kopete-3.5.10-r6/work/kopete-3.5.10

Thank you.

>
>
>>>>
>>>> Oh, and incidentally,
>>>>
>>>> No.
>>>>>Should I top-post?
>>>>
>>>> Good luck.
>>>>


1i5t5.duncan at cox

Nov 27, 2012, 12:13 PM

Post #25 of 34 (2937 views)
Permalink
Re: Dependencies of KDE 3 [In reply to]

E. Liddell posted on Tue, 27 Nov 2012 06:51:47 -0500 as excerpted:

> 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)

Note that kdm is only necessary if you use it as a graphical login. If
you login at the (CLI) shell and run startx (with kde3 set as your
XSESSION), you can avoid it entirely. I've never had it installed here,
for kde3 or kde4, as I've preferred a text login and the startx method
since my mandrake era, before gentoo (mandrake broke the *dm at one point
and I decided I didn't need it working anyway... and have never looked
back).

And if you DO prefer a graphical login, there's other *DMs available.
You aren't limited to kdm. So if it won't build for you, you can try one
of the others. If I used a *dm and not a shell login, I may be able to
list a few more, but there's at least the kde4 kdm, gdm (gtk/gnome), xdm
(generic X), and some other, slim dm (sdm?), IIRC. There may be others
I'm not aware of.

Since you already mentioned having gtk2/gnome2 on your system, gdm
shouldn't pull in too many additional deps, and xdm similarly. Others, I
don't know, except that kdm for kde4 would probably pull in more, if you
don't already have kdelibs4 installed, anyway.

kdebase-startkde provides the session files necessary for a kde xsession,
so that's the alternative to kdm for a shell login. I'm not sure whether
you can avoid it if you're using a *dm or not, but you'll for sure need
it if you're using a CLI/shell login and the startx method, as I do.

konqueror, kdesktop and konsole are run-time substitutable for other
alternatives (say gterm or xterm, there are others, for konsole), but
they may provide components that are assumed by other bits of kde (the
konsole kpart, for instance, used in kwrite/kate, konqueror, etc), so may
be required to build other bits of kde, even if you don't actually use
the apps themselves at runtime. And kdesktop is a necessary part of a
kde3 session, unless you hack that bit out of the session scripts. It
provides the actual desktop root-window, tho if it crashes you can still
continue using the rest of the kde session without it, so as I said, you
could probably hack it out of the session and replace it with something
else if you're desperate.

But for sure kdm is optional. I KNOW that, since as I said, I don't
believe I've used it since well before I switched to gentoo, and I don't
believe I've ever had it installed on gentoo since gentoo switched to the
split ebuilds (IIRC kde 3.4 era or so, definitely WELL before kde4) and I
could thus avoid it. Of course that means the metapackages that pull it
in won't install either, but you don't actually need them either, as long
as you have all the packages they pull in that you actually want,
installed, since all a metapackage is, is a list of other packages as
deps, for the convenience of those wishing to install the whole group of
dependent packages as one.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman

First page Previous page 1 2 Next page Last page  View All Gentoo desktop RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.