Bug 446458 – net-misc/tor-0.2.4.6 - checking whether Libevent is new enough for bufferevents... no

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Zenitur 2012-12-08 13:38:15 UTC]

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

[Comment 1 Jeroen Roovers (RETIRED) 2012-12-08 16:33:36 UTC]

Which version of dev-libs/libevent is installed?

[Comment 2 Anthony Basile 2012-12-08 19:38:00 UTC]

(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.

[Comment 3 Zenitur 2012-12-08 19:41:18 UTC]

My libevent has 2.0.10 version. Newest version from portage is 2.0.21.

[Comment 4 Zenitur 2012-12-08 19:42:13 UTC]

Anthony Basile, thank you.

[Comment 5 Anthony Basile 2012-12-08 19:53:25 UTC]

Okay reopen if its a problem.

[Comment 6 Zenitur 2012-12-08 19:59:12 UTC]

No, I will not. I thought that the test already exists, but the wrong.