Date: Sun, 1 Aug 1999 23:20:02 -0700 (PDT) From: Jamie Norwood <mistwolf@mushhaven.net> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/12720: gdbm (And possibly other libraries in /usr/local/lib) not usable under 3.* Message-ID: <199908020620.XAA87760@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/12720; it has been noted by GNATS. From: Jamie Norwood <mistwolf@mushhaven.net> To: Chris Piazza <cpiazza@home.net> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: misc/12720: gdbm (And possibly other libraries in /usr/local/lib) not usable under 3.* Date: Sun, 1 Aug 1999 23:15:04 -0700 Compiling things at the command line with -lgdbm should, as it did in 2.2.8, work. The /only/ way to use gdbm is using the -L flags. Maybe I am missing something important here, but given that /usr/local/lib is in the ldconfig information, it should be probed with a standard -l and not need a -L. I could be wrong, I am new to programming, but this is how it worked in 2.2.8, and how it works under Linux and Solaris... Jamie On Sun, Aug 01, 1999 at 11:09:11PM -0700, Chris Piazza wrote: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908020620.XAA87760>