This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Removal of the texinfo directory
- To: Philipp Thomas <pthomas at suse dot de>
- Subject: Re: Removal of the texinfo directory
- From: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- Date: Wed, 23 Aug 2000 16:05:24 +0200
- Cc: gcc at gcc dot gnu dot org,"Jeffrey A . Law" <law at cygnus dot com>,Richard Henderson <rth at cygnus dot com>,Mark Mitchell <mark at codesourcery dot com>
At 15:12 23.08.00, Philipp Thomas wrote:
>All my tests so far show that the texinfo directory can be removed as the
>makefiles do handle it. The only remaining issue is the installation of the
>supplied info files.
>
>The current status is, that if configure doesn't find a suitable makeinfo,
>it'll disable building *and* installation of the info files. I remember
>Richard saying that the info docs should allways be installed. The change to
>configure.in to do so would be trivial as the install-info target installs
>the info docs via INSTALL_DATA and only calls the install-info prog after
>verifying that it's the correct one.
>
>But I don't know the issues involved when trying to view info docs generated
>by a new version of makeinfo with an outdated info prog. Does that work?
>
>If yes, I would make the necessary change to configure.in and remove the
>texinfo directory from CVS.
So the removal finally will happen? :-)
While you are at it, could be please make sure the info files are no longer
built during stage1? IMHO it doesn't belong in a stage sub-make, but in the
main make. Symptom is that MAKEINFO and MAKEINFOFLAGS don't have an effect
on the info file generation.
Franz.