Patrick Swartz wrote:
> My question is now that I have downloaded the latest from the cvs tree what
> do I do now? The instruction page says "...follow the build process,
> according to the file README.build in the top level directory." After much
> searching, I can't find any README.build file.
If you're familiar with building your own kernel, then the process is
pretty similar, except that when you configure the kernel, under
Filesystems, you'll want to enable "SGI XFS filesystem support." (You'll
probably not want to enable any of the other incomplete/optional
XFS-related options for now.) You will also need to enable "Page Buffer
support." Also, to even see these options, you'll need to enable
"Prompt for development and/or incomplete code" under "Code maturity
If you're not familiar with building kernels, check out the kernel HOWTO
at http://oss.sgi.com/LDP/HOWTO/Kernel-HOWTO.html for more information.
You'll also need to build the XFS user tools. Go to the cmd/xfs
directory, and take a look at the INSTALL file. Basically, you need to
"make configure; make; make install" as root to build and install the
After the kernel, modules, and tools are compiled & installed, you're
ready to create an XFS filesystem. Take a look at
information on doing this.
> I am currently running 2.4.0-test9 on my system with all of the current
> binutils, util-linux, modutils, gcc, etc. The base system started out as a
> RH7.0 with all of RH bug fixes applied.
RH7.0 changed a few things, and you may run into a couple problems. For
starters, edit the top level Makefile in the linux/ directory, and
follow the instructions about commenting/uncommenting:
#comment out this line if compiling on RH 7.0
#CC = $(CROSS_COMPILE)gcc -V egcs-2.91.66
# AND uncomment the following line
CC = $(CROSS_COMPILE)kgcc
This will set up the right compiler for the kernel.
You should also look at linux/xfs/xfs_dir2_leaf.h, and change the line
#define XFS_DIR2_MAX_DATAPTR ((xfs_dir2_dataptr_t)0xffffffff)
#define XFS_DIR2_MAX_DATAPTR ((xfs_dir2_dataptr_t)0x7fffffff)
to get around a glibc overflow. (I guess it's time to check this in...)
Let me know if you run into any trouble,