From: milady <kami_amaterasu@hotmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Build Bug In gcc-4.1.2
Date: Fri, 11 Jan 2008 12:16:00 -0000 [thread overview]
Message-ID: <14736454.post@talk.nabble.com> (raw)
In-Reply-To: <18278.25761.322847.214726@zebedee.pink>
Hi,
I have about the same problem and I have makeinfo 4.11 installed...
$ makeinfo --version
makeinfo (GNU texinfo) 4.11
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Any I idea about why that might be???
Thanks.
Andrew Haley wrote:
>
> Thomas Dineen writes:
> > Gentle People:
> >
> > First of all I would like to thank all of you for the help you have
> > provided so far. With your help I have been able to build and install
> > Gcc versions 3.4.6 and 4.0.4.
> >
> > However I have encountered another bug in Gcc version gcc-4.1.2.
> > Shown at the bottom below. Please note that while the build complains
> > the makeinfo is not present, a makeinfo --version was successful when
> > executed in the SAME shell after the failed build. Also note that I did
> > not edit or modify the referenced .texi' or `.texinfo files.
>
> This is because for the version number in "makeinfo" is wrong. You
> need 4.4 or higher.
>
> makeinfo (GNU texinfo) 4.0
> Copyright (C) 1999 Free Software Foundation, Inc.
>
> Andrew.
>
> --
> Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
> Berkshire, SL4 1TE, UK
> Registered in England and Wales No. 3798903
>
>
--
View this message in context: http://www.nabble.com/Build-Bug-In-gcc-4.1.2-tp14243446p14736454.html
Sent from the gcc - Help mailing list archive at Nabble.com.
prev parent reply other threads:[~2008-01-10 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 21:20 Thomas Dineen
2007-12-17 11:59 ` Andrew Haley
2008-01-11 12:16 ` milady [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14736454.post@talk.nabble.com \
--to=kami_amaterasu@hotmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).