Hi all, Attached is a patch which can be applied to trunk (and other branches as well, I think) which will provide instructions to run the Module Init Tools test suite and fix BZ #1597.
I read in the bug where Matt was concerned about providing two set of instructions, this patch provides instructions to run the test suite if you wish, otherwise skip that set of instructions and go straight to the build/installation. Bottom line is there is only 1 set of instructions, with an if paragraph to run the test suite, if desired. I also added touching the modprobe.conf.5 file, even though Tush doesn't mention this in the bug. Remove this if it is not required. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 12:36:00 up 124 days, 12:09, 2 users, load average: 0.00, 0.02, 0.19
Index: chapter06/module-init-tools.xml =================================================================== --- chapter06/module-init-tools.xml (revision 6612) +++ chapter06/module-init-tools.xml (working copy) @@ -31,6 +31,17 @@ <sect2 role="installation"> <title>Installation of Module-Init-Tools</title> +<para>If you wish to run the test suite for Module-Init-Tools, download the +separate tarball and unpack it along with the source tarball. The testsuite +tarball will unpack into a <filename class='directory'>tests</filename> +directory of the source tree. Issue the following commands to perform the tests +and clean up the source tree:</para> + +<screen><userinput>./configure && +touch modprobe.conf.5 && +make check && +make distclean</userinput></screen> + <para>Module-Init-Tools attempts to rewrite its <filename>modprobe.conf</filename> man page during the build process. This is unnecessary and also relies on <command>docbook2man</command> — which is not
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page