[Clfs-support] Coreutils-6.12: help2man error

[Hugo Villeneuve]

On Sat, 13 Sep 2008 17:01:49 -0400
Joe Ciccone <jciccone at gmail.com> wrote:

> Hugo Villeneuve wrote:
> > CLFS Version: SVN-20080913-x86_64-Pure64
> >
> > Hi,
> > While compiling coreutils-6.12, I ran into the folowing problem:
> >
> > make[2]: Entering directory `/mnt/hvlinux64/tmp/coreutils-6.12/man'
> > Updating man page uname.1
> > help2man: can't get `--help' info from uname.td/uname
> > make[2]: *** [uname.1] Error 126
> > make[2]: Leaving directory `/mnt/hvlinux64/tmp/coreutils-6.12/man'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/mnt/hvlinux64/tmp/coreutils-6.12'
> > make: *** [all] Error 2
> >
> > I fixed the problem with the following line:
> >   touch man/uname.1
> > before calling make.
> >   
> This would only be needed if you applied the uname patch in the temp
> tool build. There's no need for this.

Hi Joe,
thank-you for the help.

I have a suggestion for the patches:

I'm building my clfs system from my own automated scripts. When I
install a package, any patches that fix bugs or add missing
functionality for that package are automatically applied. The scripts
look for any file that start with the package name followed by a
dash and the ".patch" extension. If some patches are optional, like
glibc libgcc_eh patch, I prefix them with "option_" like this:
option_glibc-2.7-libgcc_eh-1.patch and them I manually apply the patch.

Thus, patches handling is easier since I don't have some patches that I
apply to build the cross tools, then some different patches to apply
when I build the temporary filesystem, and then another different set
of patches to apply when I build the final system.

Hugo V.