[OpenAFS-devel] strings.h or strings.h

[Russ Allbery]

Derek Atkins <warlord@MIT.EDU> writes:

> Unfortunately this patch will #include _either_ <string.h> _OR_
> <strings.h>.  There are some systems where you need BOTH.

I really have difficulty believing this, because I've never yet written C
code that needed both and I've compiled on a pretty wide variety of
operating systems over the years.  Could you give more details on what
system really needs both headers?

I can provide configure.in macros to deal with detecting whether
strcasecmp and strcasencmp need to be prototyped if that's the problem,
and the b* function stuff can be easily fixed with:

#undef bcopy
#define bcopy(s, d, n)  memmove((d), (s), (n))
#undef bcmp
#define bcmp memcmp
#undef bzero
#define bzero(s, n)     memset((s), 0, (n))

in the everywhere-included header file until the source can be fixed.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>