Bug 22195 - Missing Documentation
Summary: Missing Documentation
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: bootstrap (show other bugs)
Version: 4.0.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: build
Depends on:
Blocks:
 
Reported: 2005-06-26 18:19 UTC by dave
Modified: 2017-11-02 04:38 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dave 2005-06-26 18:19:35 UTC
# gcc -v
Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.4/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man
--enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib
--enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux
Thread model: posix
gcc version 3.3.4 (pre 3.3.5 20040809)

# uname -a
Linux jaguar 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC 2005 i686 athlon
i386 GNU/Linux
SUSE 9.3 Professional

Replicate using:

# cd gcc-4.0.1-20050616
# mkdir objdir
# cd objdir
# ../configure --prefix=/usr/local/gcc
# make

make[2]: Entering directory `/usr/local/src/gcc-4.0.1-20050616/objdir/gcc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/src/gcc-4.0.1-20050616/objdir/gcc'
cp doc/gcc.1 doc/g++.1
cp: cannot stat `doc/gcc.1': No such file or directory
make[1]: *** [doc/g++.1] Error 1
make[1]: Leaving directory `/usr/local/src/gcc-4.0.1-20050616/objdir/gcc'
make: *** [all-gcc] Error 2

Temporary fix:

# touch gcc/doc/gcc.1
# make
Comment 1 Andrew Pinski 2005-06-26 18:31:19 UTC
I don't think this is a bug.
Reading: <http://gcc.gnu.org/install/prerequisites.html>:
Texinfo version 4.2 (or later)
Necessary for running makeinfo when modifying *.texi files to test your changes.
Necessary to build GCC documentation during development because the generated output files are not 
included in the CVS repository. They are included in releases. 

Comment 2 Andrew Pinski 2005-07-09 16:35:14 UTC
This is not a bug for a snapshot.
Comment 3 Ranjit Mathew 2006-03-31 03:43:05 UTC
FWIW, I am getting the same error with GCC 3.4.6 and I *do have* GNU Texinfo
4.8.

I have FSF GCC 3.4.5 sources and I downloaded GCC 3.4.6 diffs for "core" and
"g++" - the patches applied successfully, but "make bootstrap" terminates with
the same error as reported by the filer. I'm on i686-pc-linux-gnu and the
starting compiler is FSF GCC 3.4.5.

The command for configuration was:

/root/inst/gcc-3.4.6/configure --prefix=/usr/local --disable-debug \
--disable-nls --disable-checking --enable-threads=posix \
--enable-languages=c,c++ --enable-__cxa_atexit --with-system-zlib \
--with-gnu-ld --with-gnu-as --with-arch=pentium3 --with-tune=pentium3
Comment 4 dave 2006-03-31 05:23:00 UTC
The page at http://gcc.gnu.org/install/prerequisites.html under "Tools/packages necessary for building GCC" does NOT list "Texinfo version 4.4 (or later)" as a requirement.

I was not intending to modify GCC (as the requirements for modifying it do list Texinfo). I was intending to compile it. Out of the box compile on my system failed, and Ranjit's system. Thus a bug, no?  (And even if it still isn't deemed a bug, the fix is a simple one-liner, which I provided.)

Perhaps the term "modify" implies "CVS" -- if so, perhaps that could be emphasized on the prerequisite page? That is, "If you download GCC from the repository (regardless of whether you want to modify it or not), you must have the following ..."
Comment 5 Ranjit Mathew 2006-03-31 05:30:18 UTC
(In reply to comment #4)
> 
> I was not intending to modify GCC (as the requirements for modifying it do list
> Texinfo). I was intending to compile it. Out of the box compile on my system
> failed, and Ranjit's system. Thus a bug, no?  (And even if it still isn't
> deemed a bug, the fix is a simple one-liner, which I provided.)

When you're downloading an SVN snapshot, which is intended for developers,
you do not get much of the automatically generated stuff that's available
in releases. For SVN snapshots, you must read the "modifying GCC" portion
of the pre-requisites documentation.


> Perhaps the term "modify" implies "CVS" -- if so, perhaps that could be
> emphasized on the prerequisite page? That is, "If you download GCC from the
> repository (regardless of whether you want to modify it or not), you must have
> the following ..."

Agreed.
Comment 6 sandra 2017-11-02 03:13:21 UTC
I'm guessing a 12-year-old bug complaining that building a patched ancient development version of GCC doesn't work is no longer relevant.  Can we close this?
Comment 7 Andrew Pinski 2017-11-02 04:38:27 UTC
.