1 |
On Tue, Nov 20, 2012 at 7:38 PM, Igor Korot <ikorot01@×××××.com> wrote: |
2 |
> Hi, ALL, |
3 |
> I'm trying to install KDE 3 from kde-sunset overlay and am getting the |
4 |
> compiler error: |
5 |
> |
6 |
> |
7 |
> /bin/sh ../../libtool --silent --tag=CXX --mode=compile |
8 |
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop |
9 |
> -I../../kdecore -I. -I../../kjs -I../../kdecore/network |
10 |
> -I../../kwallet/client -I../../dcop -I../../libltdl -I../../kdefx |
11 |
> -I../../kdecore -I../../kdecore -I../../kdecore/network -I../../kdeui |
12 |
> -I../../kio -I../../kio/kio -I../../kio/kfile -I../.. |
13 |
> -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -DQT_THREAD_SUPPORT |
14 |
> -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 |
15 |
> -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith |
16 |
> -DNDEBUG -DNO_DEBUG -O2 -march=core2 -O2 -pipe -Wformat-security |
17 |
> -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions |
18 |
> -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST |
19 |
> -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o ksslsettings.lo |
20 |
> ksslsettings.cc |
21 |
> In file included from ksslsettings.cc:47:0: |
22 |
> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type |
23 |
> ./kopenssl.h:526:16: error: expected ';' before '(' token |
24 |
> ./kopenssl.h:532:17: error: 'STACK' has not been declared |
25 |
> ./kopenssl.h:538:15: error: 'STACK' has not been declared |
26 |
> ./kopenssl.h:544:18: error: expected ';' before '(' token |
27 |
> ./kopenssl.h:550:4: error: 'STACK' does not name a type |
28 |
> ./kopenssl.h:556:16: error: 'STACK' has not been declared |
29 |
> ./kopenssl.h:562:4: error: 'STACK' does not name a type |
30 |
> ./kopenssl.h:828:4: error: 'STACK' does not name a type |
31 |
> ./kopenssl.h:829:25: error: 'STACK' has not been declared |
32 |
> ksslsettings.cc: In member function 'QString KSSLSettings::getCipherList()': |
33 |
> ksslsettings.cc:157:12: error: no matching function for call to |
34 |
> 'KOpenSSLProxy::sk_num(_STACK*)' |
35 |
> ./kopenssl.h:538:8: note: candidate is: int KOpenSSLProxy::sk_num(int*) |
36 |
> ksslsettings.cc:159:20: error: 'class KOpenSSLProxy' has no member |
37 |
> named 'sk_value' |
38 |
> make[5]: *** [ksslsettings.lo] Error 1 |
39 |
> make[5]: *** Waiting for unfinished jobs.... |
40 |
> In file included from kssl.cc:47:0: |
41 |
> ./kopenssl.h:453:4: error: 'ASN1_METHOD' does not name a type |
42 |
> ./kopenssl.h:526:16: error: expected ';' before '(' token |
43 |
> ./kopenssl.h:532:17: error: 'STACK' has not been declared |
44 |
> ./kopenssl.h:538:15: error: 'STACK' has not been declared |
45 |
> ./kopenssl.h:544:18: error: expected ';' before '(' token |
46 |
> ./kopenssl.h:550:4: error: 'STACK' does not name a type |
47 |
> ./kopenssl.h:556:16: error: 'STACK' has not been declared |
48 |
> ./kopenssl.h:562:4: error: 'STACK' does not name a type |
49 |
> ./kopenssl.h:828:4: error: 'STACK' does not name a type |
50 |
> ./kopenssl.h:829:25: error: 'STACK' has not been declared |
51 |
> kssl.cc: In member function 'void KSSL::setPeerInfo()': |
52 |
> kssl.cc:616:8: error: 'class KOpenSSLProxy' has no member named 'sk_dup' |
53 |
> make[5]: *** [kssl.lo] Error 1 |
54 |
> make[5]: Leaving directory |
55 |
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl' |
56 |
> make[4]: *** [all-recursive] Error 1 |
57 |
> make[4]: Leaving directory |
58 |
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl' |
59 |
> make[3]: *** [all] Error 2 |
60 |
> make[3]: Leaving directory |
61 |
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio/kssl' |
62 |
> make[2]: *** [all-recursive] Error 1 |
63 |
> make[2]: Leaving directory |
64 |
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10/kio' |
65 |
> make[1]: *** [all-recursive] Error 1 |
66 |
> make[1]: Leaving directory |
67 |
> `/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10' |
68 |
> make: *** [all] Error 2 |
69 |
> emake failed |
70 |
> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase): |
71 |
> * died running emake, kde_src_compile:make |
72 |
> * |
73 |
> * Call stack: |
74 |
> * ebuild.sh, line 93: Called src_compile |
75 |
> * environment, line 4608: Called kde_src_compile |
76 |
> * environment, line 3187: Called kde_src_compile 'all' |
77 |
> * environment, line 3202: Called kde_src_compile 'make' |
78 |
> * environment, line 3194: Called die |
79 |
> * The specific snippet of code: |
80 |
> * emake || die "died running emake, $FUNCNAME:make" |
81 |
> * |
82 |
> * If you need support, post the output of `emerge --info |
83 |
> '=kde-base/kdelibs-3.5.10-r6'`, |
84 |
> * the complete build log and the output of `emerge -pqv |
85 |
> '=kde-base/kdelibs-3.5.10-r6'`. |
86 |
> * This ebuild used the following eclasses from overlays: |
87 |
> * /var/lib/layman/kde-sunset/eclass/kde.eclass |
88 |
> * /var/lib/layman/kde-sunset/eclass/kde-functions.eclass |
89 |
> * /var/lib/layman/kde-sunset/eclass/qt3.eclass |
90 |
> * This ebuild is from an overlay named 'kde-sunset': |
91 |
> '/var/lib/layman/kde-sunset/' |
92 |
> * The complete build log is located at |
93 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log'. |
94 |
> * The ebuild environment file is located at |
95 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'. |
96 |
> * Working directory: |
97 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10' |
98 |
> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10' |
99 |
> |
100 |
>>>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file: |
101 |
> |
102 |
>>>> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log' |
103 |
> |
104 |
> * Messages for package kde-base/kdelibs-3.5.10-r6: |
105 |
> |
106 |
> * You have the legacyssl use flag enabled, which fixes issues with some broken |
107 |
> * sites, but breaks others instead. It is strongly discouraged to use it. |
108 |
> * For more information, see bug #128922. |
109 |
> * On some setups, which rely on the correct update of utmp records, not using |
110 |
> * utempter might not update them correctly. If you experience unexpected |
111 |
> * behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled. |
112 |
> * ERROR: kde-base/kdelibs-3.5.10-r6 failed (compile phase): |
113 |
> * died running emake, kde_src_compile:make |
114 |
> * |
115 |
> * Call stack: |
116 |
> * ebuild.sh, line 93: Called src_compile |
117 |
> * environment, line 4608: Called kde_src_compile |
118 |
> * environment, line 3187: Called kde_src_compile 'all' |
119 |
> * environment, line 3202: Called kde_src_compile 'make' |
120 |
> * environment, line 3194: Called die |
121 |
> * The specific snippet of code: |
122 |
> * emake || die "died running emake, $FUNCNAME:make" |
123 |
> * |
124 |
> * If you need support, post the output of `emerge --info |
125 |
> '=kde-base/kdelibs-3.5.10-r6'`, |
126 |
> * the complete build log and the output of `emerge -pqv |
127 |
> '=kde-base/kdelibs-3.5.10-r6'`. |
128 |
> * This ebuild used the following eclasses from overlays: |
129 |
> * /var/lib/layman/kde-sunset/eclass/kde.eclass |
130 |
> * /var/lib/layman/kde-sunset/eclass/kde-functions.eclass |
131 |
> * /var/lib/layman/kde-sunset/eclass/qt3.eclass |
132 |
> * This ebuild is from an overlay named 'kde-sunset': |
133 |
> '/var/lib/layman/kde-sunset/' |
134 |
> * The complete build log is located at |
135 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/build.log'. |
136 |
> * The ebuild environment file is located at |
137 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/temp/environment'. |
138 |
> * Working directory: |
139 |
> '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10' |
140 |
> * S: '/var/tmp/portage/kde-base/kdelibs-3.5.10-r6/work/kdelibs-3.5.10' |
141 |
> |
142 |
> Also, very strange thing is that the dependency tree of KDE 3 is not updated: |
143 |
> |
144 |
> If I have the latest openssl, which is 1.0.0j, KDE will slot-instal 0.0.8x. |
145 |
> |
146 |
> Is there such an incompatibility? |
147 |
> |
148 |
> And third issue: |
149 |
> |
150 |
> mDNSResponder ebuuild is not in the tree. |
151 |
|
152 |
Was removed four months ago; this was the warning: |
153 |
|
154 |
http://archives.gentoo.org/gentoo-dev/msg_f420c354ab23da51c943dff9cb4d9e76.xml |
155 |
|
156 |
As the mail says, net-dns/avahi[mdnsresponder-compat] seems to cover |
157 |
the same; perhaps you could use that? |
158 |
|
159 |
> Could someone please put it back? |
160 |
|
161 |
Unless someone steps up to maintain it (and fix all the problems it |
162 |
could have), it's not going to happen. |
163 |
|
164 |
Regards. |
165 |
-- |
166 |
Canek Peláez Valdés |
167 |
Posgrado en Ciencia e Ingeniería de la Computación |
168 |
Universidad Nacional Autónoma de México |