> yacc -d -l ssl_expr_parse.y
> fatal error: illegal option: l, line 1
> *** Error code 1
Ok, that's perhaps my fault: The yacc target should _NEVER_ be
called for end users like you. It's for the maintainer (me)
only and I use BSD yacc which knows -l. I'll add a "touch" to
make sure the target is not called for end users.
This seems to me to be a blemish on an otherwise excellent package.
Modssl is supposed to be a source distribution and the .y file is
part of the source. The y.tab.c file generated from the .y should
be thought of as an intermediate non-source file, like the assembly
file generated by the C compiler.
I'm not sure what the -l option in BSD yacc does. If it's something
important and Bison doesn't do it and you can't manage without it,
please write to [EMAIL PROTECTED] saying that Bison is missing a
useful feature that you need, and hopefully Bison's maintainers will
add the feature to the next version of Bison. GNU systems (including
most Linux-based systems) use Bison partly because it does some things
that BSD yacc doesn't; in fact I think that building GCC from sources
requires Bison. If modssl won't compile from source (meaning
including the .y) on a standard Linux system, that seems like a
shortcoming that should really be addressed. Otherwise, any modssl
source package (rpm, debian package, etc.) should have a dependency
for BSD yacc, so the user automatically install yacc to compile modssl.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
