FreeBSD linking problem

[Godmar Back]

Why not add them to the end, so that standard libs installed
in /usr/local/lib are still found, but the newly built libs
will still override any garbage you may have in /usr/local/lib?

Secondly, a test in configure for this situation would be nice.

	- Godmar


> On Apr 22, 1999, David Jones <dej at inode.org> wrote:
> 
> > The problem?  Kaffe is linked using -lkaffevm, and libkaffevm is dynamic.
> > So, ld searched my LD_LIBRARY_PATH for it.  The old library, installed in
> > /usr/local/lib, was hit first, and ld couldn't find the symbols.  Choke.
> 
> Nope, it has nothing to do with LD_LIBRARY_PATH or libkaffevm being
> dynamic or not.  The problem is that kaffe's configure.in
> automatically adds -L/usr/local/lib and -I/usr/local/include to
> LDFLAGS and CPPFLAGS, respectively, in a way that they're searched
> before files living in the source or build tree.  So pre-installed
> versions of libraries and headers may be used instead of newer ones.
> 
> IMO, that's a good argument for not adding those directories to the
> standard search paths unless the user explicitly says so.
> 
> -- 
> Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
> {oliva,Alexandre.Oliva}@dcc.unicamp.br  aoliva@{acm.org,computer.org}
> oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
> *** E-mail about software projects will be forwarded to mailing lists
> 
>