NetBSD/tools/compat/sys/sha1.h

/*	$NetBSD: sha1.h,v 1.1 2006/10/29 06:17:08 dogcow Exp $	*/

/* We unconditionally use the NetBSD SHA1 in libnbcompat. */
#include "nbtool_config.h"
#include "../../sys/sys/sha1.h"
cross (and native) building works again. woo. 2006-10-29 09:17:08 +03:00			`/* $NetBSD: sha1.h,v 1.1 2006/10/29 06:17:08 dogcow Exp $ */`
* Always include the NetBSD glob(3) in libnbcompat, as the host tools use some features of glob(3) that are not available on all systems. * Always include the NetBSD vis(3) in libnbcompat, since vis(3) is not really standardized, and the vis(3) present on some systems is different from ours. * Always include the NetBSD MD2, MD4, MD5, RMD160, and SHA1 implementations in libnbcompat. The host tools use features of the NetBSD versions which aren't present on all systems that include those functions. * Add a check for random(3) -- the Heimdal host tools want it. * Add a check for termios.h -- the Heimdal host tools want it. * Update the README to indicate the current state of building the host tools on Solaris 8 (for SPARC). 2002-09-13 23:07:01 +04:00
			`/* We unconditionally use the NetBSD SHA1 in libnbcompat. */`
Overhaul how `build.sh tools' are used: * Rename "config.h" to "nbtool_config.h" and HAVE_CONFIG_H to HAVE_NBTOOL_CONFIG_H. This makes in more obvious in the source when we're using tools/compat/config.h versus "standard autoconf" config.h * Consistently move the inclusion of nbtool_config.h to before <sys/cdefs.h> so that the former can provide __RCSID() (et al), and there's no need to protect those macros any more. These changes should make it easier to "tool-ify" a program by adding: #if HAVE_NBTOOL_CONFIG_H #include "nbtool_config.h" #endif to the top of the source files (for the general case). 2003-10-27 03:12:41 +03:00			`#include "nbtool_config.h"`
Adjust pathnames to {md{4,5},sha1}.h after their removal from src/include. Approved by mrg@ 2003-10-01 15:59:06 +04:00			`#include "../../sys/sys/sha1.h"`