From owner-freebsd-bugs Sun Aug 1 23:10:41 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 50CD614BF9 for ; Sun, 1 Aug 1999 23:10:38 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA86852; Sun, 1 Aug 1999 23:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 1 Aug 1999 23:10:01 -0700 (PDT) Message-Id: <199908020610.XAA86852@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Chris Piazza Subject: Re: misc/12720: gdbm (And possibly other libraries in /usr/local/lib) not usable under 3.* Reply-To: Chris Piazza Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/12720; it has been noted by GNATS. From: Chris Piazza To: freebsd-gnats-submit@freebsd.org, mistwolf@mushhaven.net Cc: Subject: Re: misc/12720: gdbm (And possibly other libraries in /usr/local/lib) not usable under 3.* Date: Sun, 1 Aug 1999 23:09:11 -0700 This is not a problem with the port or package of gdbm, it is a problem with the configure scripts. Here's a fancy fix: % env LDFLAGS="-L/usr/local/lib" ./configure [..] checking for dbm_close in -lgdbm... yes checking for main in -lresolv... no checking for getpwnam in -lsun... no checking for main in -lseq... no checking for main in -lintl... yes Conclusion: It's not the gdbm port's problem that these configure scripts don't check /usr/local/lib. I'll close this PR if you don't object. -Chris -- cpiazza@home.net cpiazza@FreeBSD.org "I don't like principles. I prefer prejudices." -Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message