[Sebastian Dröge] > I did some more testing. It happens only if libfl-dev is installed, > which was on my system but is not part of the build dependencies. > > So this should either become part of Build-Conflicts or has to be > fixed, but it's less bad than I thought :) > > To solve it, one can link with libfl.a instead of libfl.so apparently.
I believe this only happen with older autoconf/automake macros. Not sure exactly what trigger it, but todays release seem to have fixed it by using AC_PROG_LEX(noyywrap) in configure.ac. I do not believe it is because libfl-dev is installed but because a autoconf macro is misbehaving. I believe it is fixed in 0.4.2. -- Happy hacking Petter Reinholdtsen
