1 This file describes how to build findutils starting from a set of code
2 checked out of CVS, rather than from a released source distribution.
6 * A C compiler, linker and software development libraries (the standard
8 * GNU Autoconf version 2.61 or later (earlier versions *may* work)
9 * GNU Automake version 1.9 or later (earlier versions *may* work)
10 * GNU m4 version 1.4 or later
11 * GNU gettext (unless you use configure --disable-nls)
13 2. Generate a gnulib installation within the fileutils source tree
15 Change your working directory to the findutils source directory (that
16 is, the directory containing this file). Then run the following
21 This command will use CVS to check out the version of gnulib which is
22 intended to work with the findutils source you already have, as
23 configured by the file import-gnulib.config. The gnulib code itself
24 is left in the directory "gnulib-cvs". The "gnulib" directory
25 contains just the gnulib files that findutils needs during the build
28 If you want to build findutils with a different version of gnulib,
29 just edit import-gnulib.config to change the version and then re-run
30 import-gnulib.sh. When specifying the version, you can specify
31 either the date or a CVS tag. If making any kind of release, please
32 use a fully identifying version (rather than just, say, "HEAD").
34 The import-gnulib.sh script will also run Autoconf and Automake to
35 generate the "configure" script and "Makefile.in" files. Should you
36 need to do this manually, you can do it like this :-
38 aclocal -I m4 -I gnulib/m4 && \
41 automake --add-missing --copy
44 3. Run "configure" and "make" in the normal way.
46 If you have GNU libintl installed, you can just run "configure".
47 Otherwise, run "configure --disable-nls".