infrastructure and using that infrastructure in programs.
* MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building
of the infratsructure (libraries, support programs, etc.)
* USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control
building of support for using the corresponding API
in various libraries/programs that can use it.
As discussed on tech-toolchain.
- make a copy of cfparse.y called "y.tab.y" because "cfparse.h" is not
actually the yacc generated header file (duh?)
- include the tcpdump directory with -I *after* racoon's source, else
tcpdump's headers will be picked up unexpectedly
- include . *before* racoon's source so as to make the generated files
first on the list
bundle proposal interpretation, and some other fixes.
XXX WARNS?=0 in racoon/Makefile is necessary to compile yacc-generated files
(static function, generated by yacc, is never used).