Should configure error out if lex/flex is missing?
After successfully running ./configure for syslog-ng 3.2beta1, the build immediately failed because I didn't have flex installed. I see that configure is already calling AM_PROG_LEX...so maybe this is just the expected behavior? After installing flex the build completed successfully.
On Mon, 2010-10-18 at 10:49 -0400, Lars Kellogg-Stedman wrote:
After successfully running ./configure for syslog-ng 3.2beta1, the build immediately failed because I didn't have flex installed. I see that configure is already calling AM_PROG_LEX...so maybe this is just the expected behavior? After installing flex the build completed successfully.
you shouldn't need flex if you try to compile syslog-ng from a tarball and you didn't modify cfg-lex.l does it still need it? maybe the timestamps are bogus in the tarball. so, no it shouldn't error out, but at the same time it shouldn't call flex/bison at all. -- Bazsi
you shouldn't need flex if you try to compile syslog-ng from a tarball and you didn't modify cfg-lex.l
I believe I was building from the git repository. So never mind :).
Hi, Anyway I've added some checks for flex in the configure script just to warn if it wasn't found: commit 1217ca65b5b42c3a215e8c28bca4683643b4a0c4 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Tue Oct 19 17:26:00 2010 +0200 check for flex at configure time and warn the user if it is not present On Tue, 2010-10-19 at 11:14 -0400, Lars Kellogg-Stedman wrote:
you shouldn't need flex if you try to compile syslog-ng from a tarball and you didn't modify cfg-lex.l
I believe I was building from the git repository. So never mind :).
-- Bazsi
participants (2)
-
Balazs Scheidler
-
Lars Kellogg-Stedman