Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Nov 2005 17:15:48 GMT
From:      "Scot W. Hetzel" <swhetzel@gmail.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/89023: USE_BDB doesn't set name of Berkely dB, or location of the include directory
Message-ID:  <200511141715.jAEHFmfE039558@www.freebsd.org>
Resent-Message-ID: <200511141720.jAEHKEr9043582@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         89023
>Category:       ports
>Synopsis:       USE_BDB doesn't set name of Berkely dB, or location of the include directory
>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:   Mon Nov 14 17:20:14 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Scot W. Hetzel
>Release:        FreeBSD 5.x-STABLE
>Organization:
>Environment:
>Description:
            I noticed that when the USE_BDB is used to provide a LIB_DEPENDS on a particular version of Berkley dB, that it doesn't define BDB_LIB_NAME or the BDB_INCLUDE_DIR.  Without these variables defined the port maintainers that include USE_BDB in their ports, will have to define these variables for themselves.

I also noticed that the USE_BDB, doesn't honor the WITH_BDB_VER variable, instead it is left up to the ports maintainer to define the variable.
>How-To-Repeat:
              Have a look at the security/cyrus-sasl2 and */kdesdk3 ports on how they are defining the location of the Berkley dB include directory and the name of the Berkley db library.  And their use of WITH_BDB_VER.
>Fix:
              See the attached patches in the next message:
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511141715.jAEHFmfE039558>