gcc-20020429 make info failure

gcc-20020429 make info failure

[Neal D. Becker]

gcc-20020429 i686-pc-linux-gnu:
Reading specs from /opt/gcc-3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../../gcc-20020429/configure --prefix=/opt/gcc-3.1
Thread model: single
gcc version 3.1 20020429 (prerelease)

make info
make[1]: Entering directory `/usr/local/src/i686/gcc-3.1/libiberty'
make[2]: Entering directory `/usr/local/src/i686/gcc-3.1/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/src/i686/gcc-3.1/libiberty/testsuite'
make[1]: Leaving directory `/usr/local/src/i686/gcc-3.1/libiberty'
make[1]: Entering directory `/usr/local/src/i686/gcc-3.1/libiberty'
makeinfo  -I../../../gcc-20020429/libiberty ../../../gcc-20020429/libiberty/libiberty.texi
make[2]: Entering directory `/usr/local/src/i686/gcc-3.1/libiberty/testsuite'
make[2]: Nothing to be done for `info'.
make[2]: Leaving directory `/usr/local/src/i686/gcc-3.1/libiberty/testsuite'
make[1]: Leaving directory `/usr/local/src/i686/gcc-3.1/libiberty'
make[1]: Entering directory `/usr/local/src/i686/gcc-3.1/zlib'
make[1]: Nothing to be done for `info'.
make[1]: Leaving directory `/usr/local/src/i686/gcc-3.1/zlib'
make[1]: Entering directory `/usr/local/src/i686/gcc-3.1/gcc'
cd ../../../gcc-20020429/gcc && makeinfo   -I doc -I doc/include -o doc/cpp.info doc/cpp.texi
cd ../../../gcc-20020429/gcc && makeinfo   -I doc -I doc/include -o doc/gcc.info doc/gcc.texi
doc/invoke.texi:8377: Misplaced {.
doc/invoke.texi:8377: Misplaced }.
doc/invoke.texi:8378: Misplaced {.
doc/invoke.texi:8378: Misplaced }.
doc/invoke.texi:8446: Misplaced {.
doc/invoke.texi:8446: Misplaced }.
doc/invoke.texi:8448: Misplaced {.
doc/invoke.texi:8448: Misplaced }.
makeinfo: Removing output file `doc/gcc.info' due to errors; use --force to preserve.
make[1]: *** [../../../gcc-20020429/gcc/doc/gcc.info] Error 2
make[1]: Leaving directory `/usr/local/src/i686/gcc-3.1/gcc'
make: *** [do-info] Error 1

Re: gcc-20020429 make info failure

[Joseph S. Myers]

On 1 May 2002, Neal D. Becker wrote:

> make info

The info and install-info targets aren't documented as targets for users
installing GCC; you must expect failures if you use them with the effect
of bypassing the configure checks on the installed makeinfo version.

I've applied (mainline and 3.1 branch) the following patch to update
the documentation of required makeinfo version in install.texi.

Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/gcc/gcc/ChangeLog,v
retrieving revision 1.13905
diff -u -r1.13905 ChangeLog
--- ChangeLog	1 May 2002 08:27:42 -0000	1.13905
+++ ChangeLog	1 May 2002 12:57:35 -0000
@@ -1,3 +1,8 @@
+2002-05-01  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* doc/install.texi: Update Texinfo version requirement
+	documentation.
+
 2002-05-01  Jakub Jelinek  <jakub@redhat.com>
 
 	PR target/6512, PR target/5628
Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.107
diff -u -r1.107 install.texi
--- doc/install.texi	30 Apr 2002 18:04:42 -0000	1.107
+++ doc/install.texi	1 May 2002 12:57:36 -0000
@@ -916,7 +916,7 @@
 not need Bison installed to build them.
 
 When building from CVS or snapshots, or if you modify Texinfo
-documentation, you need version 4.0 or later of Texinfo installed if you
+documentation, you need version 4.1 or later of Texinfo installed if you
 want Info documentation to be regenerated.  Releases contain Info
 documentation pre-built for the unmodified documentation in the release.
 
@@ -1346,7 +1346,7 @@
 @uref{../bugs.html,,bug reporting guidelines}.
 
 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
-dvi}.  You will need to have @command{texi2dvi} (version at least 4.0)
+dvi}.  You will need to have @command{texi2dvi} (version at least 4.1)
 and @TeX{} installed.  This creates a number of @file{.dvi} files in
 subdirectories of @file{@var{objdir}}; these may be converted for
 printing with programs such as @command{dvips}.  You can also
@@ -3363,7 +3363,7 @@
 @end html
 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
 PowerPC system in big endian mode running NetBSD@.  To build the
-documentation you will need Texinfo version 4.0 (NetBSD 1.5.1 included
+documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
 Texinfo version 3.12).
 
 @html

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: gcc-20020429 make info failure

[Neal D. Becker]

But why didn't "make install" install the info in the first place?
What is the correct procedure?

Re: gcc-20020429 make info failure

[Joseph S. Myers]

On 1 May 2002, Neal D. Becker wrote:

> But why didn't "make install" install the info in the first place?
> What is the correct procedure?

"make install" will install the info files if present.  They'll be present 
if makeinfo >=4.1 was installed when you configured, or if you use a 
release or prerelease tarball instead of a snapshot or CVS.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: gcc-20020429 make info failure

[Neal D. Becker]

Are pre-processed info files available anywhere?  I'd like to see what
new optimization options I can play with, but I don't have
makeinfo-4.1 and don't want to bother installing it.

Re: gcc-20020429 make info failure

[Joseph S. Myers]

On 1 May 2002, Neal D. Becker wrote:

> Are pre-processed info files available anywhere?  I'd like to see what
> new optimization options I can play with, but I don't have
> makeinfo-4.1 and don't want to bother installing it.

Prerelease tarballs (in the releases directory on the FTP site) include
the info files.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: gcc-20020429 make info failure

[David O'Brien]

On Wed, May 01, 2002 at 02:06:39PM +0100, Joseph S. Myers wrote:
> I've applied (mainline and 3.1 branch) the following patch to update
> the documentation of required makeinfo version in install.texi.

Can you also document the requirement of Perl 5.6 in order to build the
manpages?

Re: gcc-20020429 make info failure

[Alexandre Oliva]

On May  1, 2002, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:

> The info and install-info targets aren't documented as targets for users
> installing GCC

Hmm...  IIRC, install-info is one of the blessed targets in the GNU
Coding Standards.  It's expected to work, even if it does nothing.  If
we don't have info files to install, it should succeed.  If it
currently fails, we may be in need of a work around.  Not that this
should delay the release (given that info files will be present in the
release), just something I thought I'd point out.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Re: gcc-20020429 make info failure

[Joseph S. Myers]

On 2 May 2002, Alexandre Oliva wrote:

> Hmm...  IIRC, install-info is one of the blessed targets in the GNU
> Coding Standards.  It's expected to work, even if it does nothing.  If
> we don't have info files to install, it should succeed.  If it
> currently fails, we may be in need of a work around.  Not that this
> should delay the release (given that info files will be present in the
> release), just something I thought I'd point out.

info is one of the standard targets, install-info isn't.  (The
install-info problem was in fastjar (which has no manual at all); the
install-info target in gcc does work if the info files aren't present.) I
don't see anything in the standards saying whether the info target should
fail if makeinfo isn't present or recent enough, but I don't see any
problem with it failing when makeinfo is too old, given that we include
info files in releases and configure so that "make bootstrap" doesn't
attempt to rebuild info when makeinfo is too old.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: gcc-20020429 make info failure

[Alexandre Oliva]

On May  2, 2002, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:

> info is one of the standard targets, install-info isn't.

How odd...  I could swear it used to be the other way round a couple
of years ago.  I stand corrected.

> I don't see any problem with it failing when makeinfo is too old,
> given that we include info files in releases

Agreed.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer