This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstrap failure: gcc/install.texi:1074: Unknown command `uref
- To: egcs-bugs at egcs dot cygnus dot com
- Subject: Re: Bootstrap failure: gcc/install.texi:1074: Unknown command `uref
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Wed, 24 Feb 1999 12:32:04 +0100 (MET)
- cc: Jeffrey A Law <law at cygnus dot com>, Dave Love <d dot love at dl dot ac dot uk>
On Mon, 22 Feb 1999, Jeffrey A Law wrote:
>> Making info file `cpp.info' from `/sw/swtest/egcs/egcs/gcc/cpp.texi'.
>> makeinfo -I/sw/swtest/egcs/egcs/gcc -o gcc.info
>> /sw/swtest/egcs/egcs/gcc/gcc.texi
>> /sw/swtest/egcs/egcs/gcc/install.texi:1074: Unknown command `uref'.
>> /sw/swtest/egcs/egcs/gcc/install.texi:1074: Misplaced `{'.
>> /sw/swtest/egcs/egcs/gcc/install.texi:1074: Misplaced `}'.
>> Making info file `gcc.info' from `/sw/swtest/egcs/egcs/gcc/gcc.texi'.
>> gmake[2]: *** [gcc.info] Error 2
> This looks like you're not picking up makeinfo from the build tree.
and Dave Love wrote:
> Isn't this just picking up an old makeinfo?
I checked by instrumenting gcc/Makefile.in accordingly and indeed
`makeinfo` was invoked (which leads to an old version) instead of
the version in the egcs object tree.
Note that $OBJECTTREE/texinfo/makeinfo/makeinfo *does* exist.
To me this seems to be a bug:
Shouldn't we always prefer our self-built makeinfo over any that might be
installed already? (If and only if our makeinfo binary exists, that is.)
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/