patch to unhook libxpg4 and liby from build

[Chris Pressey]

On Sat, 27 Mar 2004 23:52:35 -0800
Chris Pressey <cpressey at xxxxxxxxxxxxxxx> wrote:

> On Sat, 27 Mar 2004 23:26:33 -0800 (PST)
> Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> >     Isn't yyerror() is a standard bison/yacc procedure?  Where is
> >     yyerror() coming from if not from liby?
> 
> It seems to be provided by the program which is using yacc in each
> case. I guess the idea was that if the program didn't provide it's own
> yyerror(), it could fall back on the one provided by liby.  But none
> of ours rely on that.

This situation is not made much clearer by our documentation for yacc,
which is pretty scant and doesn't mention liby.  It does, however,
mention POSIX.2, and I just realized that I can download that now.

It says that the application can supply main() and yyerror(), or that
these routines can be obtained from the yacc library.

So, in order to remain POSIX.2 compliant, we do have to keep liby
around.  On the other hand, there's no obligation for our programs to
link to it if they don't use anything from it.

-Chris