[OpenAFS] Need SYS_NAME_ID_i386_nbsd_16

[Jeffrey Hutzelman]

On Monday, February 09, 2004 14:56:23 -0600 John Hascall <john@iastate.edu> 
wrote:

>
>> of course if you look at the cvs head, 2600 is used. you're not doing
>> something dumb like porting 1.2 are you?
>
> Yes.  I tried openafs-1.3.52 and openafs-snap-2004-01-23
> both of which seem not at all ready for prime time...
>
> For example, snap-2004-01-23 (apparently the latest)
> didn't have a configure, and trying to make one was
> not good:
>
> rhovanion: {559} autoconf
> configure.in:2: error: possibly undefined macro: AM_INIT_AUTOMAKE
>       If this token and others are legitimate, please use
> m4_pattern_allow.       See the Autoconf documentation.

Well, yeah, you didn't build it correctly.
See 'regen.sh' in the top level.

> 1.3.52 had a configure script at least, but the make takes a crap early:

> cd src && cd pinstall && make all
> cc  -O -I/home/john/openafs-1.3.52/src/config -I. -I.
> -I/home/john/openafs-1.3.52/include
> -I/home/john/openafs-1.3.52/include/afs
> -I/home/john/openafs-1.3.52/include/rx -I/home/john/openafs-1.3.52
> -I/home/john/openafs-1.3.52/src -I/home/john/openafs-1.3.52/src -O2 -pipe
> ./install.c -o pinstall   install.c: In function `quickStrip':
> install.c:446: error: structure has no member named `a_magic'
> *** Error code 1

Yeah, this is where you start porting.  The code in question is 
architecture-specific, since it knows about the binary executable format. 
You may need to write some code, or you may find what you need is already 
there, but not compiled on your platform (you may have to adjust ifdef's).

If you haven't done it before, you should be aware that porting OpenAFS to 
a new platform is not an easy task.  Everyone's kernel internals are 
different, and the documentation on both sides is generally pretty poor.

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