"Gabor Z. Papp" <[EMAIL PROTECTED]> writes:
> Just trying install gimp from cvs. Installed latest automake
> cvs before. Export ACLOCAL_AMFLAGS, and gimp's autogen.sh
> complains about m4 files, and suggest using ACLOCAL_FLAGS. I
> unset _AMFLAGS, and set _FLAGS, and it seems, that works.
I think
On Mar 24, 2000, Tom Tromey <[EMAIL PROTECTED]> wrote:
> Try doing "LEX=flex" and "YACC=bison" in configure.in before running
> the macros. Bleah.
Even better:
LEX=${LEX-flex}
YACC=${YACC-bison}
So the user can override these variables, if s/he doesn't have flex or
bison in the PATH.
Sascha>
Sascha> I don't specify -lfl and I don't use LIBS, so I can not use
Sascha> LIBADD instead.
I don't understand this.
Anyway, the current automake doesn't force you to link with @LEXLIB@.
Neither did automake 1.4, if I remember correctly.
So I don't understand why you are seeing -lfl on your link
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
| Use LIBADD rather than LIBS. LIBS use used by all libraries, while
| LIBADD must be specified individually for each library.
Akim Demaille <[EMAIL PROTECTED]> writes:
| Just don't use -lfl at all.
I don't specify -lfl and I don't use LIBS, so I ca
> "Sascha" == Sascha Ziemann <[EMAIL PROTECTED]> writes:
Sascha> bin_PROGRAMS = rlpd rlpc
Sascha> rlpd_SOURCES = rlpd.c rlp.c errwrap.c conf_parser.y conf_lexer.l
Sascha> rlpc_SOURCES = rlpc.c rlp.c errwrap.c
Sascha> How can I prevent the second program (rlpc) from beeing linked
Sascha> with
> "Sascha" == Sascha Ziemann <[EMAIL PROTECTED]> writes:
Sascha> One needs -lfl and the other not.
Just don't use -lfl at all. It contains a dummy main, which you
certainly already have available somewhere else, and a dummy yywrap,
which you can write: return 1. Alternatively, use %option
