[MacPorts] #22423: radlib doesn't use MacPorts libraries

[Ryan Schmidt]

On Nov 11, 2009, at 00:08, M. Brooks Clark wrote:

> I don't see why raddebug is linking with /usr/lib/libsqlite3.dylib.
>
> The libtool line looks like this:
>
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.2  -O2 - 
> arch x86_64 -L../src/.libs   -L/usr/lib -L/usr/local/lib  -L/opt/ 
> local/lib -o raddebug raddebug.o -lc -lm -lrad   -lsqlite3 -lm -lc
>
> libtool: link: /usr/bin/gcc-4.2 -O2 -arch x86_64 -o .libs/raddebug  
> raddebug.o  -L/opt/local/var/macports/build/ 
> _Users_mbclark_Dropbox_ports_devel_radlib/work/radlib-2.8.4/ 
> src/.libs -L/usr/lib -L/usr/local/lib -L/opt/local/lib /opt/local/ 
> var/macports/build/_Users_mbclark_Dropbox_ports_devel_radlib/work/ 
> radlib-2.8.4/src/.libs/librad.dylib -lsqlite3 -lm -lc
>
> Maybe I'm wrong here, but I thought the -L option added directories  
> to the *beginning* of the search path, so shouldn't /opt/local/lib  
> be first in the search path?

As far as I understand, -L adds directories to the end of the search  
path. But I haven't tested that extensively.