Serghei, we have multile errors with GCC 4.8, have you migrated to it yet? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 19 July 2013 13:31:53 Ilya Chernykh wrote:
Serghei, we have multile errors with GCC 4.8, have you migrated to it yet?
Yes, I succesully built KDE3 on Fedora 19 (GCC 4.8.1). What kind of errors you have, in what packages? -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 19 July 2013 15:47:18 Serghei Amelian wrote:
Serghei, we have multile errors with GCC 4.8, have you migrated to it yet?
Yes, I succesully built KDE3 on Fedora 19 (GCC 4.8.1). What kind of errors you have, in what packages?
Most notably, in kdebase3, but overall in 15 packages. Mostly problems with typedef. This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net. What do you think? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 19 July 2013 13:39:56 Ilya Chernykh wrote:
On Friday 19 July 2013 15:47:18 Serghei Amelian wrote:
Serghei, we have multile errors with GCC 4.8, have you migrated to it yet?
Yes, I succesully built KDE3 on Fedora 19 (GCC 4.8.1). What kind of errors you have, in what packages?
Most notably, in kdebase3, but overall in 15 packages. Mostly problems with typedef.
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 19 July 2013 16:00:36 Serghei Amelian wrote:
Serghei, we have multile errors with GCC 4.8, have you migrated to it yet?
Yes, I succesully built KDE3 on Fedora 19 (GCC 4.8.1). What kind of errors you have, in what packages?
Most notably, in kdebase3, but overall in 15 packages. Mostly problems with typedef.
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try.
Where can I find the most up-to-date version? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Saturday 20 July 2013 09:43:55 Ilya Chernykh wrote: [...]
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
https://github.com/serghei -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Sunday 21 July 2013 00:22:06 Serghei Amelian wrote:
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
I looked through the kdebase commits but still cannot see any GCC 4.8 fixes. Do you experience errors like this? [ 417s] In file included from ./kcontrol/crypto/kcm_crypto_la_all_cpp.cpp:3:0: [ 417s] ./kcontrol/crypto/crypto.cpp: In member function 'void KCryptoConfig::slotCAImport()': [ 417s] ./kcontrol/crypto/crypto.cpp:1844:41: error: 'class KOpenSSLProxy' has no member named 'X509_STORE_new' [ 417s] X509_STORE *certStore = KOSSL::self()->X509_STORE_new(); [ 417s] ^ [ 417s] ./kcontrol/crypto/crypto.cpp:1845:43: error: 'class KOpenSSLProxy' has no member named 'X509_STORE_add_lookup' [ 417s] X509_LOOKUP *certLookup = KOSSL::self()->X509_STORE_add_lookup(certStore, KOSSL::self()->X509_LOOKUP_file()); [ 417s] ^ [ 417s] ./kcontrol/crypto/crypto.cpp:1845:91: error: 'class KOpenSSLProxy' has no member named 'X509_LOOKUP_file' [ 417s] X509_LOOKUP *certLookup = KOSSL::self()->X509_STORE_add_lookup(certStore, KOSSL::self()->X509_LOOKUP_file()); [ 417s] ^ [ 417s] In file included from /usr/include/openssl/x509.h:600:0, [ 417s] from /usr/include/openssl/ssl.h:156, [ 417s] from ./kcontrol/crypto/crypto.cpp:76, [ 417s] from ./kcontrol/crypto/kcm_crypto_la_all_cpp.cpp:3: [ 417s] ./kcontrol/crypto/crypto.cpp:1848:21: error: 'class KOpenSSLProxy' has no member named 'X509_LOOKUP_ctrl' [ 417s] KOSSL::self()->X509_LOOKUP_load_file(certLookup, [ 417s] ^ [ 417s] In file included from ./kcontrol/crypto/kcm_crypto_la_all_cpp.cpp:3:0: [ 417s] ./kcontrol/crypto/crypto.cpp:1840:31: error: 'class KOpenSSLProxy' has no member named 'sk_num' [ 417s] #define sk_num KOSSL::self()->sk_num [ 417s] ^ [ 417s] /usr/include/openssl/safestack.h:143:2: note: in expansion of macro 'sk_num' [ 417s] sk_num(CHECKED_STACK_OF(type, st)) [ 417s] ^ [ 417s] ./kcontrol/crypto/crypto.cpp:1841:33: error: 'class KOpenSSLProxy' has no member named 'sk_value' [ 417s] #define sk_value KOSSL::self()->sk_value [ 417s] ^ [ 417s] /usr/include/openssl/safestack.h:145:11: note: in expansion of macro 'sk_value' [ 417s] ((type *)sk_value(CHECKED_STACK_OF(type, st), i)) [ 417s] ^ [ 417s] ./kcontrol/crypto/crypto.cpp:1921:35: error: 'class KOpenSSLProxy' has no member named 'X509_STORE_free' [ 417s] if (certStore) { KOSSL::self()->X509_STORE_free(certStore); [ 417s] ^ [ 417s] ./kcontrol/crypto/crypto.cpp:1993:32: error: 'class KOpenSSLProxy' has no member named 'X509_STORE_free' [ 417s] if (certStore) KOSSL::self()->X509_STORE_free(certStore); [ 417s] ^ https://build.opensuse.org/project/monitor/KDE:KDE3?blocked=0&building=0&dispatching=0&finished=0&scheduled=0&signing=0&succeeded=0 -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Sunday 21 July 2013 00:22:06 Serghei Amelian wrote:
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
Do you build kcm_crypto component? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 23 July 2013 07:37:41 Ilya Chernykh wrote:
On Sunday 21 July 2013 00:22:06 Serghei Amelian wrote:
This time I think it would be better to just make efforts and build Trident rather than applying isolated patches, if you have the ported source on the net.
What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
Do you build kcm_crypto component?
I think I didn't. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 23 July 2013 20:05:20 Serghei Amelian wrote:
What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
Do you build kcm_crypto component?
I think I didn't.
How did you avoid building it? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 23 July 2013 20:25:32 Ilya Chernykh wrote:
On Tuesday 23 July 2013 20:05:20 Serghei Amelian wrote:
> What do you think?
Sure, we can try.
Where can I find the most up-to-date version?
Do you build kcm_crypto component?
I think I didn't.
How did you avoid building it?
In cmake I have a flag named WITH_SSL, if it's set to OFF, it will be disabled. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 23 July 2013 21:40:37 Serghei Amelian wrote:
> > What do you think? > > Sure, we can try.
Where can I find the most up-to-date version?
Do you build kcm_crypto component?
I think I didn't.
How did you avoid building it?
In cmake I have a flag named WITH_SSL, if it's set to OFF, it will be disabled.
Well, now with SSL disabled it builds ok. Seems kio_crypto is not compatible with gcc 4.8. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 24 July 2013 06:06:55 Ilya Chernykh wrote:
On Tuesday 23 July 2013 21:40:37 Serghei Amelian wrote:
> > > What do you think? > > > > Sure, we can try. > > Where can I find the most up-to-date version?
Do you build kcm_crypto component?
I think I didn't.
How did you avoid building it?
In cmake I have a flag named WITH_SSL, if it's set to OFF, it will be disabled.
Well, now with SSL disabled it builds ok. Seems kio_crypto is not compatible with gcc 4.8.
Or maybe is not compatibile with newer OpenSSL. I wil check. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (2)
-
Ilya Chernykh -
Serghei Amelian