This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/12730] manual page install broken with old Pod::man
- From: "cgd at broadcom dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Oct 2003 18:29:04 -0000
- Subject: [Bug other/12730] manual page install broken with old Pod::man
- References: <20031022182218.12730.cgd@broadcom.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12730
------- Additional Comments From cgd at broadcom dot com 2003-10-22 18:29 -------
investigating this, it looks like this is fallout from:
2003-10-20 Kelley Cook <kcook@gcc.gnu.org>
* Makefile.in: Get parsedir and docobjdir from configure.
* configure.in: Recogonize --enable-generated-files-in-srcdir.
Pass along parsedir and docobjdir.
* configure: Regenerate.
* doc/install.texi: Document --enable-generated-files-in-srcdir.
that patch ultimately causes docobjdir to be set to a dir in the obj tree
if --enable-generated-files-in-srcdir isn't set. But it doesn't do anything
to create the manual pages there if the manual-page-generation tools
aren't up to date.
(BTW, I think it's **great** that the files won't be generated in the source
directory any more, but IMO it should still be possible to build/install GCC
without being able to regen all generated files.)