[OpenAFS] Porting to new platforms

[Nathan Neulinger]

I attempted to do this for parisc-linux, and got to where everything
would compile, and the lwp tests and such worked right, as well as user
space client tools. Kernel testing however hit a snag due to some
screwed up module loader problem that has still not been fixed. 

I'd strongly suggest trying to get it ported in the trunk. Some of the
changes there should make it easier to port, and it will certainly make
it more likely to be included in future versions.

Most of the codebase is fairly generic, but there are some very
architectural specific things in various places, especially lwp. You
should probably pick a model architecture that is close to what you
need, and look for any ifdef's throughout the source referring to that
AFS_XXXX_ENV. 

-- Nathan

On Sat, 2003-04-05 at 14:36, Ryan Underwood wrote:
> Hi,
> 
> This may be slightly offtopic for -info, but I'm not subscribed to -devel
> and only have a short question.
> 
> I would like to port OpenAFS to Linux/MIPS.  I started with the Debian package
> of OpenAFS 1.2.8.  Scanning through the tree, I located various
> platform-dependent build configs and Makefiles, renamed, hacked up, etc as
> necessary and got the base packages to build.  However, when building the
> kernel module, I'm getting some very strange errors that I've never seen
> before.
> 
> So here are my questions:
> 1) Is the codebase fairly generic (i.e. portable C) so that a build can
> target mostly any Unix platform?
> 2) What sort of special massaging should the kernel module need for a
> new platform, if any?
> 
> If there is interest, I will post the weird stuff that happened during the
> module compile.
> 
> Thanks!
-- 

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216