Summary: | www-client/lynx-2.8.7_p1 does not show SSL enabled pages with USE=gnutls | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vasilis Lourdas <bugs> |
Component: | New packages | Assignee: | Wormo (RETIRED) <wormo> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | bug, dberkholz, jesse, martin.holzer |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | lynx ebuild with '--enable-gnutls-compat' |
Description
Vasilis Lourdas
2009-10-17 11:30:57 UTC
Version 2.8.6-r2 does not exhibit the issue. Thanks for reporting this problem. It is definitely reproducible when USE flag gnutls is enabled, so I guess most people use openssl rather than gnutls. I have been poking through the lynx configure scripts to figure out how to make gnutls option work, but in the meantime you can get lynx ssl working by emerging with USE="ssl -gnutls". Alert!: This client does not contain support for HTTPS URLs. please fix this ASAP this is also for x86 Created attachment 231429 [details]
lynx ebuild with '--enable-gnutls-compat'
Hi,
As said in the ebuild file :
# --with-gnutls and --with-ssl are alternatives,
# the latter enabling openssl support so it should be
# _not_ be used if gnutls ssl implementation is desired
for now, these two flags are exclusive !
Perhaps, there's a better way to solve that, I've tested on ~x86 with succes
to simply add '--enable-gnutls-compat' flag when gnutls use flag is on :
< myargs="$myargs --with-gnutls" # ssl implementation = gnutls
---
> myargs="$myargs --with-gnutls --enable-gnutls-compat" # ssl implementation = gnutls
As the current version is 2.8.8 you find in attachent my modified ebuild file for it...
www-client/lynx-2.8.8_pre2 USE="bzip2 gnutls ipv6 nls unicode -cjk -ssl" Still unable to browse HTTPS www sites. ATM, disabling gnutls and enabling ssl worked for me, although i have both of the libraries installed. Does this still occur in the latest versions in the tree? I can't reproduce it with 2.8.8_pre9 that I just added to CVS. (In reply to comment #9) > Does this still occur in the latest versions in the tree? I can't reproduce > it with 2.8.8_pre9 that I just added to CVS. ping! Closing as obsolete since it should be fixed in 2.8.8_pre12. |