Re: AM_PROG_LEX does not set LEXLIB properly

[Alexandre Duret-Lutz]

>>> "Pete" == Pete Ryland <address@hidden> writes:

 Pete> My configure.in has the AM_PROG_LEX macro in it.  On a machine here[1]
 Pete> (that I don't maintain) we have flex installed at /opt/sfw/ and the
 Pete> configure script quite happily sets the variable LEXLIB to -lfl and the
 Pete> conftest passes.  However, I end up with the following error:

AM_PROG_LEX is just a wrapper around AC_PROG_LEX, an Autoconf
macro; Automake itself does not set LEXLIB.  Could you show us
the `config.log' excerpt related to the flex/-lfl tests?  It's
dubious that this test passes if libfl is not in your ld path.

[...]

 Pete> I'm thinking that it may be a good idea to have LEXLIB also include a
 Pete> -L/path/to/libfl.a option.  Or am I just confused?

I'd say users should run 
  ./configure LDFLAGS=-L/any/non-standard/place

or this sytem could have a PREFIX/share/config.site (see the Autoconf manual)

I can't see how AC_PROG_LEX could guess this path.  

 Pete> And BTW, when I try to set LD to gld (the name of the binary for GNU ld
 Pete> on the system) it again works for the conftests, but then reverts back
 Pete> to /usr/ccs/bin/ld for the actual compilation.

That works for me.  The ld used during linking comes from Libtool:

% ./configure LD=gld 
[...]
% grep LD= ./libtool
LD="gld"

-- 
Alexandre Duret-Lutz