Documentation build failure

[Daniel Fischer]

make-ing 7.0.2 failed with:

-- everything fine up to here, users guide html okay

Build users_guide.ps
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/openSUSE)
entering extended mode
latex failed
users_guide_tmp.tex:1631: Undefined control sequence \Documents.
users_guide_tmp.tex:1631: leading text: }
users_guide_tmp.tex:1631: Undefined control sequence \user.
users_guide_tmp.tex:1631: leading text: }
users_guide_tmp.tex:3993: Undefined control sequence \Person.
users_guide_tmp.tex:3993: leading text:       or \nolinkurl{Data\Person.hs}
users_guide_tmp.tex:6185: Undefined control sequence \Documents.
users_guide_tmp.tex:6185: leading text: 
...ts~And~Settings\user\ghc\package.conf.d}
users_guide_tmp.tex:6185: Undefined control sequence \user.
users_guide_tmp.tex:6185: leading text: 
...ts~And~Settings\user\ghc\package.conf.d}
users_guide_tmp.tex:6185: Undefined control sequence \ghc.
users_guide_tmp.tex:6185: leading text: 
...ts~And~Settings\user\ghc\package.conf.d}
users_guide_tmp.tex:6185: Undefined control sequence \package.
users_guide_tmp.tex:6185: leading text: 
...ts~And~Settings\user\ghc\package.conf.d}
users_guide_tmp.tex: File ended while scanning use of \hyper at n@rmalise.
users_guide_tmp.tex: Emergency stop.
Error: latex compilation failed
make[1]: *** [docs/users_guide/users_guide.ps] Fehler 1
make: *** [all] Fehler 2

on openSUSE 11.3.

I don't know which programme is at fault here, maybe someone can check 
whether ps/pdf documentation building works on other systems.

Re ./configure-ing after setting

BUILD_DOCBOOK_PS = NO
BUILD_DOCBOOK_PDF = NO

in mk/build.mk said it would build ps and pdf documentation nevertheless, I 
had to edit the configure script to convince it not to try.
configure just checks for the existence of a dblatex command, so perhaps

$ dblatex --version
/usr/lib/python2.6/site-packages/dbtexmf/dblatex/grubber/util.py:8: 
DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
dblatex version 0.2.7

is helpful information.


Unrelated:

The build produces several

SpecConstr
    Function `$j_s8qC{v} [lid]'
      has four call patterns, but the limit is 3
    Use -fspec-constr-count=n to set the bound
    Use -dppr-debug to see specialisations

warnings(?) (this is also very common building libraries).

a) What does that mean for code generation? Will the specialisations be 
generated nevertheless?
b) Would it be reasonable to have a higher default than 3 for spec-constr-
count?

Cheers,
Daniel