Subject: Re: Use of libtool in pkgs (correction)
To: Todd Vierling <>
From: Perry E. Metzger <>
List: tech-pkg
Date: 07/15/1998 12:37:11
Could the Package.txt file be updated with this stuff?

And in fact, could it be put in CVS in the top directory of pkgsrc?


Todd Vierling writes:
> One minor nit about the libtool instructions:
> : When linking programs that depend on thse libraries _before_ they are
> : installed, preface the cc or ld line with "${LIBTOOL} --mode=link", and it
> : will find the correct libraries (static or shared).
> I found that libtool will not allow you to specify a relative path in -L
> (such as -L../somelib), because it is trying to force you to change that
> argument to be the .la file.  For example:
> ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
> won't work; it needs to be changed to:
> ${LIBTOOL} --mode=link ${CC} -o someprog ../somelib/
> and it will DTRT with the libraries.  If you *must* use a relative path with
> -L, and you are not going to run this program before installing it, you can
> omit the use of libtool during link and install of this program if you add
> the subdirectory ".libs" in your -L command:
> ${CC} -o someprog -L../somelib/.libs -lsomelib
> This is less preferable to the method above.
> -- 
> -- Todd Vierling (Personal; Bus.