Date: Sat, 15 Feb 2014 13:56:09 GMT From: Matthew Rezny <matthew@reztek.cz> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/186792: dns/unbound fails to build with option LIBEVENT20 Message-ID: <201402151356.s1FDu9JC032900@cgiserv.freebsd.org> Resent-Message-ID: <201402151400.s1FE00GG091563@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 186792 >Category: ports >Synopsis: dns/unbound fails to build with option LIBEVENT20 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 15 14:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Matthew Rezny >Release: 10.0-STABLE >Organization: RezTek, s.r.o. >Environment: FreeBSD desktop.reztek 10.0-STABLE FreeBSD 10.0-STABLE #0 r261871: Fri Feb 14 16:41:18 CET 2014 root@desktop.reztek:/usr/obj/usr/src/sys/DESKTOP amd64 >Description: Attempting to build unbound-1.4.21_1 with OPTIONS = ECDSA PYTHON THREADS LIBEVENT20 fails. There are several screens full of errors that are essentially all a variation on the pattern: .libs/netevent.o: In function '[all of them]' util/netevent.c:(.text+offset): undefined reference to 'event_[something]' It seemed plainly obvious that essentially none of the symbols from libevent2 were being resolved during linking. Indeed, the buid succeeds with no LIBEVENT option of with LIBEVENT14 option set. The version of libevent2 that unbound failed to link with is 2.0.21. The version of libevent that unbound succeeding in linking with is 1.4.14b_3. >How-To-Repeat: cd /usr/ports/dns/unbound make config (select LIBEVENT20) make install clean (watch it fail) >Fix: workaround: cd /usr/ports/dns/unbound make config (select LIBEVENT14 or unset all LIBEVENT options) make install clean (succeeds) >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402151356.s1FDu9JC032900>