Peter Eisentraut <peter_e@gmx.net> writes:
> I think I can explain this behavior. When building outside the source
> tree, in looks in the build tree and then in the source tree for
> documentation to install. This is done by looking for a 'html'
> directory. When you already have an 'html' directory in the source tree
> before you run configure, an 'html' directory is also created in the
> build tree, because the build tree is created by making an empty copy of
> every directory in the source tree. So then it thinks the documentation
> is present in the build tree and installs that, but the directory is
> empty, so nothing is installed.
Hm, but prep_buildtree doesn't create an html_stamp file in the build
tree, so this explanation doesn't seem to hold water completely. Why
didn't it try to build new docs in the build tree?
regards, tom lane
