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.
5 * CVS (to check out findutils itself)
6 * git (to check out the gnulib code)
7 * A C compiler, linker and software development libraries (the standard
9 * GNU Autoconf version 2.61 or later (earlier versions *may* work)
10 * GNU Automake version 1.9 or later (earlier versions *may* work)
11 * GNU m4 version 1.4 or later
12 * GNU gettext (unless you use configure --disable-nls)
14 2. Generate a gnulib installation within the fileutils source tree
16 Change your working directory to the findutils source directory (that
17 is, the directory containing this file). Then run the following
22 This command will use CVS to check out the version of gnulib which is
23 intended to work with the findutils source you already have, as
24 configured by the file import-gnulib.config. The gnulib code itself
25 is left in the directory "gnulib-git". The "gnulib" directory
26 contains just the gnulib files that findutils needs during the build
29 If you want to build findutils with a different version of gnulib,
30 just edit import-gnulib.config to change the version and then re-run
31 import-gnulib.sh. When specifying the version, you can specify
32 either the date or a CVS tag. If making any kind of release, please
33 use a fully identifying version (rather than just, say, "HEAD").
35 The import-gnulib.sh script will also run Autoconf and Automake to
36 generate the "configure" script and "Makefile.in" files. Should you
37 need to do this manually, you can do it like this :-
39 aclocal -I m4 -I gnulib/m4 && \
42 automake --add-missing --copy
44 3. (Optional) Update the translations
46 rsync -Lrtvz translationproject.org::tp/latest/findutils/ po
48 3. Run "configure" and "make" in the normal way.
50 If you have GNU libintl installed, you can just run "configure".
51 Otherwise, run "configure --disable-nls".