Date: Thu, 17 Jun 1999 23:16:09 -0400 From: Brandon Fosdick <bfoz@glue.umd.edu> To: Nathan Ahlstrom <nrahlstr@winternet.com> Cc: Dan Nelson <dnelson@emsphone.com>, FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Linking libraries on 3.2-S Message-ID: <3769B9F9.24A60AD6@glue.umd.edu> References: <37697EC6.4FA99E8@glue.umd.edu> <19990617183928.A44151@portage.winternet.com> <376996EE.887EADCB@glue.umd.edu> <19990617213029.B9746@dan.emsphone.com> <19990617213340.A13740@winternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nathan Ahlstrom wrote: > > 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 Ah. Now I get it. It would be nice to have someplace to set compile-time paths. How about /etc/make.conf? How would I use autoconf? Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" 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?3769B9F9.24A60AD6>