gnutls-2.8.3 doesn't seem to install the libgnutls-config tool, which the configure system of weechat relies on to find the library, hence, ssl is disabled at configure time, though the ssl use flag remains set of course. This drove me mad for a couple of days until I decided to look closely at the configure output. Reproducible: Always Steps to Reproduce: 1.install gnutls 2.8.3 2.(re)compile weechat 3.start weechat, and see that you cannot connect to any ssl server, even though you have the ssl use flag enabled, the error message will tell you that the ssl support hasn't been compiled into weechat, which turned to be true in the end Actual Results: ssl is disabled but the use flag tell you otherwise Expected Results: ssl should be enabled if you enable the relevant use flag I am not sure about the right solution to this one. Weechat could either be updated to work with gnutls, or maybe the ebuild could ask for <=gnutls-2.6.6, which works ok. If there are more packages with this problem maybe it's gnutls which should be masked until this is sorted. No idea. I just report what I have found about the problem.
OK, this is a request for an update - this problem was solved in weechat 0.2.6.3. BTW, you failed to tell which version of weechat has this problem (well, in this particular case it didn't matter, but next time it may).
(In reply to comment #1) > OK, this is a request for an update - > this problem was solved in weechat 0.2.6.3. Well, I wasn't completely sure how to solve it, that's why the bug report was that fuzzy. > BTW, you failed to tell which version of weechat > has this problem (well, in this particular case > it didn't matter, but next time it may). It happened with all versions in portage at that moment as you say. I didn't know that there was a new version upstream that solved the problem. By the time I posted the bug I wasn't quite sure if the problem was about weechat or about gnutls either. Thanks for the quick answer and for identifying the problem.
You did the identifying, I'd just took a look at weechat's webpage.
I've just added weechat-0.2.6.3 to CVS which should fix this issue.
(In reply to comment #4) > I've just added weechat-0.2.6.3 to CVS which should fix this issue. > Thanks.
