Simon Wilkinson 8e27248698 Always include afsconfig.h
Our coding standards say that OpenAFS source files should always have
 #include <afsconfig.h>
 #include <afs/param.h>
at the start of the file. Including just param.h, or having these
includes in a different order can produce unexpected effects, because
param.h includes sysnames.h, which in turn includes stds.h, which may
rely upon having the results of configure tests available.

Fix the obvious places in the Unix build which get this wrong.

Change-Id: I081f04dab30a6bbb49fe71d3ac2d7c11e231e2f5
Reviewed-on: http://gerrit.openafs.org/1912
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>
2010-05-06 11:52:08 -07:00
..
2010-02-09 09:07:09 -08:00
2010-04-26 17:57:35 -07:00
2009-07-09 22:58:37 -06:00
2010-04-15 15:56:05 -07:00
2010-05-06 11:52:08 -07:00
2010-04-15 15:56:05 -07:00
2010-04-15 15:56:05 -07:00
2008-11-29 18:08:33 +00:00
2009-07-12 17:49:32 -06:00
2010-02-17 10:49:18 -08:00
2009-11-17 13:12:57 -08:00
2010-04-15 15:56:05 -07:00
2010-04-15 15:56:05 -07:00
2009-10-08 08:00:13 -07:00
2009-11-17 13:12:57 -08:00

NOTE: fc_cbc_encrypt now modifies its 5th argument, to permit chaining over
scatter/gather vectors.