Date: Mon, 6 Aug 2007 11:44:48 +0100 (BST) From: Neil Darlow <neil@darlow.co.uk> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/115241: dar binary is liked against existing libdar Message-ID: <20070806104448.AA705102D31@router.darlow.co.uk> Resent-Message-ID: <200708061100.l76B04aN028601@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 115241 >Category: ports >Synopsis: dar binary is liked against existing libdar >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 06 11:00:04 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Neil Darlow >Release: FreeBSD 6.2-RELEASE-p7 i386 >Organization: >Environment: System: FreeBSD router.darlow.co.uk 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #0: Thu Aug 2 18:15:16 BST 2007 root@router.darlow.co.uk:/usr/obj/usr/src/sys/ROUTER i386 >Description: sysutils/dar links dar binary against existing libdar in /usr/local/lib instead of the libdar which has just been built. This results in build failures due to unresolved externals when the libdar API changes like recently when going from version 2.3.3 to 2.3.4. >How-To-Repeat: Update dar-2.3.3 to 2.3.4 using e.g. portupgrade >Fix: A workaround is to deinstall then reinstall the port but a proper fix would be to correct the library search path in the port to link against the just-built libdar. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070806104448.AA705102D31>