Date: Thu, 17 Jun 1999 21:33:40 -0500 From: Nathan Ahlstrom <nrahlstr@winternet.com> To: Dan Nelson <dnelson@emsphone.com>, Brandon Fosdick <bfoz@glue.umd.edu> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Linking libraries on 3.2-S Message-ID: <19990617213340.A13740@winternet.com> In-Reply-To: <19990617213029.B9746@dan.emsphone.com>; from Dan Nelson on Thu, Jun 17, 1999 at 09:30:29PM -0500 References: <37697EC6.4FA99E8@glue.umd.edu> <19990617183928.A44151@portage.winternet.com> <376996EE.887EADCB@glue.umd.edu> <19990617213029.B9746@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh yeah, duh! ;-) So for compiling his only option is the -L flag? That clears some confusion up hopefully. Thanks, Nathan > You're confusing run-time link paths with compile-time link paths. > ldconfig is only used at runtime, to resolve shared library > dependencies. -L flags on the gcc line are only used at link time, to > resolve both shared and static library dependencies. > > ldconfig paths can be specified in /etc/rc.conf. Unfortunately, > there's no place to add compile-time library paths. Most software uses > autoconf to scan common directories for the libraries it needs. > > -Dan Nelson > dnelson@emsphone.com -- Nathan Ahlstrom FreeBSD: http://www.FreeBSD.org/ nrahlstr@winternet.com PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990617213340.A13740>