| Summary: | qt4 problem with openssl-0.9.8g | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Radu Benea <radu_benea2002> |
| Component: | [OLD] Library | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | jmroca, oyvinds |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Radu Benea
2008-04-06 17:17:01 UTC
Hi, I can reproduce this. Konqueror of KDE4 can't connect to any HTTPS sites, Kopete (KDE4 too) can't connect any protocol that uses SSL / TLS like MSN Messenger or Jabber/Gtalk. I'm open to do some tests but I need some help. Here is a patch for this bug: http://cvs.fedoraproject.org/viewcvs/rpms/qt/devel/qt-x11-opensource-src-4.3.4-openssl.patch?rev=1.1&view=markup How to apply to a custom ebuild on my local overlay? Is SHLIB_VERSION_NUMBER defined somewhere for properly usage in Gentoo? I'll follow this track to provide help if I can. Thanks. No, I already tried applying that patch... aparently it doesn't work on gentoo... and with modifying local ebuilds... copy file to files in the corresponding directory from /usr/portage/... add your file to PATCHES="..." field.. check other ebuild to see how this is done... when you finish, type ebuild $ebuild_name digest, after this you can emerge it I copied the original qt.ebuild into my local overlay and added a line "epatch" with this patch and copied the patch into the files directory. I'm not sure if this is the right method, but I really sure that the patch has been applied as I expected. After emerge this custom ebuild that applies the patch, the bug persists so yes, it seems that doesn't works on gentoo. Qt builds but no changes on the behavior. I reviewed too the Qt 4.4 sources for the solution and it seems quite more complex that the patch provides. It seems that the bug (if really exists :P) has been solved in Qt 4.4, so... we can patiently wait. *** Bug 219362 has been marked as a duplicate of this bug. *** If the problem reappears in current Qt versions, feel free to reopen. |