> 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.
Bison seems to not be fully compatible. I was trying to compile Grass 5.0
beta (a GIS package from baylor.edu) a couple weeks ago. It had a .y file
with C code included underneath the yacc grammar. When bison processed it,
it ended up with some of the code in the wrong place (a function was used
before being declared I believe). I switched to Berkeley yacc and that
fixed it (and I didn't bother to figure out what was different, since it
worked). But that's about the extent of my knowledge about yacc, so I guess
I'll quit yacking already...
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
