From owner-freebsd-ports@FreeBSD.ORG Mon Mar 28 19:42:52 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7740D1065678; Mon, 28 Mar 2011 19:42:52 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2AB378FC0C; Mon, 28 Mar 2011 19:42:52 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id p2SJgpxL028755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Mar 2011 12:42:51 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9F2FE1CC0C; Mon, 28 Mar 2011 12:42:51 -0700 (PDT) To: Doug Barton In-reply-to: Your message of "Mon, 28 Mar 2011 11:47:49 PDT." <4D90D7D5.1060509@FreeBSD.org> Date: Mon, 28 Mar 2011 12:42:51 -0700 From: "Kevin Oberman" Message-Id: <20110328194251.9F2FE1CC0C@ptavv.es.net> Cc: ports@freebsd.org, umq@ueo.co.jp, delphij@FreeBSD.org Subject: Re: Unable to configure dirmngr after openldap upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2011 19:42:52 -0000 > Date: Mon, 28 Mar 2011 11:47:49 -0700 > From: Doug Barton > > This has nothing to do with libksba, it's just a coincidence that > bumping the PORTREVISION on dirmngr for the libksba update caused you to > rebuild dirmngr against an up to date openldap. > > Reverting to openldap-client-2.4.24 allows dirmngr to build, thus I've > changed the subject line of this message. The presence of the FETCH > option (which is what I always use anyway) doesn't improve the > situation, FYI. > > > Doug > > > On 03/28/2011 11:22, Kevin Oberman wrote: > > After I upgraded libksba to 1.2.0, I attempted to re-build dirmngr, but > > all of my systems are failing due to failing to detect LDAP. > > > > checking whether LDAP via "-lldap" is present and sane... no > > checking whether LDAP via "-lldap -llber" is present and sane... no > > checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no > > checking whether LDAP via "-lwldap32" is present and sane... no > > checking for ANSI C header files... (cached) yes > > checking for string.h... (cached) yes > > checking locale.h usability... yes > > checking locale.h presence... yes > > checking for locale.h... yes > > checking for an ANSI C-conforming const... yes > > checking for inline... inline > > checking for size_t... yes > > checking return type of signal handlers... void > > checking whether sys_siglist is declared... yes > > checking for byte typedef... no > > checking for ushort typedef... yes > > checking for ulong typedef... no > > checking for struct sigaction... yes > > checking for sigset_t... yes > > checking for sys/stat.h... (cached) yes > > checking for unistd.h... (cached) yes > > checking direct.h usability... no > > checking direct.h presence... no > > checking for direct.h... no > > checking if mkdir takes one argument... no > > checking for memicmp... no > > checking for stpcpy... yes > > checking for strsep... yes > > checking for strlwr... no > > checking for strtoul... yes > > checking for memmove... yes > > checking for stricmp... no > > checking for strtol... yes > > checking for memrchr... yes > > checking for isascii... yes > > checking for timegm... yes > > checking for getrusage... yes > > checking for setrlimit... yes > > checking for stat... yes > > checking for setlocale... yes > > checking for flockfile... yes > > checking for funlockfile... yes > > checking for funopen... yes > > checking for fopencookie... no > > checking for gmtime_r... yes > > checking for getaddrinfo... yes > > checking for strtoull... yes > > checking for mmap... yes > > checking for canonicalize_file_name... no > > configure: > > *** > > *** You need a LDAP library to build this program. > > *** Check out > > *** http://www.openldap.org > > *** for a suitable implementation. > > *** > > configure: error: > > *** > > *** Required libraries not found. Please consult the above messages > > *** and install them before running configure again. > > *** > > ===> Script "configure" failed unexpectedly. > > Please report the problem to umq@ueo.co.jp [maintainer] and attach the > > "/usr/ports/security/dirmngr/work/dirmngr-1.1.0/config.log" including the > > output of the failure of your make command. Also, it might be a good idea to > > provide an overview of all packages installed on your system (e.g. an `ls > > /var/db/pkg`). > > *** Error code 1 > > > > Stop in /usr/ports/security/dirmngr. > > *** Error code 1 > > > > I certainly do have openldap-client installed. I even re-installed it, > > just to make sure nothing had been stepped on. I have libldap and > > liblber in /usr/local/lib/ > > > > The first two attempts fail with: > > /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' > > > > Any idea what may be going wrong? > > > > -- > > Nothin' ever doesn't change, but nothin' changes much. > -- OK Go > > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.com/ > Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll take a look at CHANGES and see if I can figure out what broke the inclusion of fetch(3) support if I get a bit of time. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751