patch to unhook libxpg4 and liby from build

[Matthew Dillon]

: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

    Yes, I agree.  You need to keep the -ly stuff that's in our .mk file(s),
    but you can remove the explicit -ly linking from random utility program
    Makefile's... basically your remove_-ly_from_Makefiles.diff patch
    without the sys.mk change.

    Note that this might bite us in the ass later on if bison/yacc start
    producing calls to auxillary routines that are expected to exist 
    (be added to) liby, we'd have to add all those -ly's back, but it isn't
    a problem now so go ahead.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>