[OpenAFS] Suse 9.3 Professional RPMS

[Jeffrey Hutzelman]

On Friday, April 14, 2006 10:00:40 AM -0700 Russ Allbery <rra@stanford.edu> 
wrote:

> David Sonenberg <dsonenberg@strozllc.com> writes:
>
>> Well I went and rechecked the md5 hash(it was ok), deleted the source
>> tree and recreated it from the tar ball(bz2), and still no sys/types.h.
>> Here are the exact steps I took:
>
>> tar xjvf openafs-1.4.0-src.tar.bz2
>> cd openafs-1.4.0
>> configure --prefix=/
>> make
>
> Make sure that you have your system core development packages installed.
> It sounds like you're missing standard headers.


So, apparently no one is actually paying attention here.  The original
poster quoted the following error message:

> In file included from /root/openafs-1.4.0/include/afs/afs_sysnames.h:25,
>                  from /root/openafs-1.4.0/include/afs/param.h:58,
>                  from
> 
/root/openafs-1.4.0/src/libafs/MODLOAD-2.6.11.4-20a-smp-SP/afs_atomlist.c:11:
> /root/openafs-1.4.0/include/afs/stds.h:14:23: sys/types.h: No such file
> or directory


He's building a kernel module, or trying to.  The headers in /usr/include
are for use by user-mode code only; that tree will not and must not be
searched while building kernel code.

The problem here is that the "sys" symlink in the module build directory
(in this case, /root/openafs-1.4.0/src/libafs/MODLOAD-2.6.11.4-20a-smp-SP)
points somewhere useless.  This is probably because the required kernel
source package is not installed.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA