On 07/31/2012 03:00 AM, Akim Demaille wrote:
> So there would be two kinds of tarballs: those made with
> Flex, and those without.
Sorry, I wasn't clear enough. It's fine to require
the *maintainer* to have 'flex', so there would be only
one tarball, one with all the examples extracted from
the manual nicely. The point is that there should be no
need to require that the *builder* must have 'flex'.
If you're too busy for this I could take a crack at it.
Alas, the git master doesn't build for me. When I
try to check it out and run './bootstrap' (this is
on Fedora 15, by the way, not Solaris) it fails
with the tail end of the log being as follows:
prefix=lib/
running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install
--no-recursive -I m4
autoreconf: Entering directory `.'
autoreconf: running: true
autoreconf: running: aclocal -I m4 -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /home/eggert/opt/Linux-x86_64/autoconf-2.69/bin/autoconf
--include=m4
configure.ac:125: error: possibly undefined macro: AC_PROG_GNU_M4
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /home/eggert/opt/Linux-x86_64/autoconf-2.69/bin/autoconf failed
with exit status: 1
./bootstrap: autoreconf failed
