* Required packages - libuuid-devel or uuid-dev - libmount-devel or libmount-dev - libblkid-devel or libblkid-dev - libselinux-devel or libselinux1-dev (*1) *1: required only if supporting selinux context mount options without     using libmount.  By default, libmount is used and support of the     context mount depends on the libmount that distro provides.* How to compile $ ./configure $ makeIf your system is a 64-bit architecture and libraries are installedinto /usr/lib64 instead of /usr/lib, change the library directory with--libdir option: $ ./configure --libdir=/usr/lib64If your want to separate the library files into a subdirectory, specifyit as follows, for example: $ ./configure --libdir=/usr/lib64/nilfsIf /etc/mtab is not a symlink to /proc/self/mounts but a regular filein the target system, run the configure script with --without-libmountoption: $ ./configure --without-libmountThis configures the build environment so as to make legacymount/umount helpers (mount.nilfs2 and umount.nilfs2), in which thelegacy mtab file is handled properly.  For CentOS 6 (and other RHEL 6clones), for instance, this options is needed.* Trouble shootingIf the blkid library in your environment is old and unusable to thispackage, you can use --without-blkid option: $ ./configure --without-blkidHowever, use of this option is normally not recommended because itdisables the safety check of mkfs.nilfs2 which prevents users fromunexpectedly overwriting an in-use device.You can compile legacy mount.nilfs2 and umount.nilfs2 without supportof selinux context mount options (-o context=<context>, etc): $ ./configure --without-libmount --without-selinuxFor helpers built with mount library (libmount), support of thecontext mount depends on the libmount that distro provides.If you are having problems due to the missing nilfs2 disk format orioctl interface definition file (nilfs2_ondisk.h or nilfs2_api.h,respectively), try installing the Linux kernel source or header filepackage first.If you still cannot install these files, or if you want to overwritethem with files from this package, specify the"--enable-uapi-header-install" option as an argument to the configurescript.  This will install the uapi header files included in thispackage: $ ./configure --enable-uapi-header-installNote that the utility package itself references bundled local headerfiles, so you don't need to install these files with this option tobuild.* How to get development sources $ cd your-work-directory $ git clonehttps://github.com/nilfs-dev/nilfs-utils.gitBefore compiling the development sources, you need to run autogen.shscript.  This is not required for packaged sources unless you changedthe configuration.  $ cd nilfs-utils $ ./autogen.sh* Developer's notesThe central resource for nilfs-utils development is the mailing list(linux-nilfs@vger.kernel.org).First, please read the following documents (in short, follow Linuxkernel development rules):https://docs.kernel.org/process/coding-style.htmlhttps://docs.kernel.org/process/submitting-patches.htmlThen, check your patches with the patch style checker prior tosubmission (scripts/checkpatch.pl) like the following example: $ ./scripts/checkpatch.pl <patch-file> ... <patch-file> has no obvious style problems and is ready for submission.