| Summary: | net-misc/tor-0.2.4.6 - checking whether Libevent is new enough for bufferevents... no | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Zenitur <Zenitur> |
| Component: | Current packages | Assignee: | Anthony Basile <blueness> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | jer |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Log file | ||
Which version of dev-libs/libevent is installed? (In reply to comment #1) > Which version of dev-libs/libevent is installed? I recently dropped the check on the libevent version from the ebuild because the tree only has libevent-2.0.19 and above which is more than recent enough. Only people who's systems are very much out of date will still have an old libevent around. In this case, it has been over a year since libevent-2.0.13 was punted: 27 Nov 2011. I recall a some Council decision that 1 year is the time limit for how long we allow systems to get out of sync. My libevent has 2.0.10 version. Newest version from portage is 2.0.21. Anthony Basile, thank you. Okay reopen if its a problem. No, I will not. I thought that the test already exists, but the wrong. |
Created attachment 331804 [details] Log file emerge -av tor ... done! [ebuild U ] net-misc/tor-0.2.4.6_alpha [0.2.2.23_alpha] USE="bufferevents%* stats%* threads%* upnp%* -nat-pmp% (-selinux) -tor-hardening% -transparent-proxy% -web% (-debug%)" 3,133 kB ... checking whether we can detect the Libevent version... yes checking whether Libevent is new enough for bufferevents... no configure: error: Libevent does not seem new enough to support bufferevents. We require 2.0.13-stable or later