A directory will be automatically created for binaries to be written
into with this name when you build.
- alpha_dux40, alpha_dux50, alpha_dux51 (client does not work)
alpha_linux26
alpha_nbsd15, alpha_nbsd16
amd64_fbsd_80, amd64_fbsd_81, amd64_fbsd_82, amd64_fbsd_83,
amd64_fbsd_93, amd64_fbsd_100, amd64_fbsd_101
amd64_linux26
amd64_nbsd20, amd64_nbsd30, amd64_nbsd40
- arm_linux26
+ arm_linux26, arm64_linux26
hp_ux11i, hp_ux110, hp_ux1123 (See notes below for information on
getting missing header)
hp_ux102 (Client port possible, but db servers and utilities work)
last kernel you built for, the previous kernel module will be
overwritten.
- The Linux 2.4 series (and older) are no longer supported. The OpenAFS 1.6
- series of releases are the last ones supporting those old kernels and in
- particular their LinuxThreads.
+ The minimum supported Linux kernel is 2.6.18.
E HP-UX 11.0 Notes
F OpenBSD Notes
If you need to run regen.sh to make the configure script, you should
- first install autoconf-2.59, then setenv AUTOCONF_VERSION 2.59.
+ set the environment variable AUTOCONF_VERSION to the installed autoconf
+ version, e.g. 'setenv AUTOCONF_VERSION 2.64' (see 'J' below).
You need kernel source installed to build OpenAFS. Use the
--with-bsd-kernel-headers= configure option if your kernel source is
G FreeBSD Notes
- The FreeBSD client supports FreeBSD 8.x and later, but does not receive
- regular testing on versions older than FreeBSD 9.x at this time. Only
- the amd64 and i386 architectures are supported, but it should not be
- hard to port to other processors if they are already supported under
- another operating system.
+ The FreeBSD client supports FreeBSD 10.x and later. Only the amd64
+ and i386 architectures are supported, but it should not be hard to
+ port to other processors if they are already supported under another
+ operating system.
You need kernel source installed to build OpenAFS. Use the
--with-bsd-kernel-headers= configure option if your kernel source is
YFLAGS
Additional flags to pass to yacc.
+
+J Creating 'configure'
+
+ Normally you can use the configure script provided with the OpenAFS release
+ tar file, but if you are patching the autoconf logic or building directly
+ from source pulled from the git repository you may need to (re-)generate
+ the configure script.
+
+ To create the configure script autoconf-2.64 or later and libtool-1.9b or
+ later are needed.
+
+ Running the script 'regen.sh' creates the configure script. In addition
+ to creating the configure script, regen.sh will also, by default, build
+ the man pages, which requires the pod2man utility. Use 'regen.sh -q' to
+ skip building the man pages.
+
+ It is possible to create the configure script on one system to be used on
+ another. Ensure that the files created by 'regen.sh' are copied to the
+ target system.
\ No newline at end of file