public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Han Jiang <oglops@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: help with compiling gcc-4.1.2 on CentOS 6.3 x64
Date: Wed, 21 Nov 2012 06:41:00 -0000	[thread overview]
Message-ID: <CAKOQZ8yF6hNanErUonvmAmA9yH89tgxY6iEAODQt5GYDG+DLww@mail.gmail.com> (raw)
In-Reply-To: <CAPiRsUXPa3=edvynJdYx4AVWoG177MruK05M5mXaoRW1G54ssw@mail.gmail.com>

On Tue, Nov 20, 2012 at 10:23 PM, Han Jiang <oglops@gmail.com> wrote:

> WARNING: `makeinfo' is missing on your system.  You should only need it if
>          you modified a `.texi' or `.texinfo' file, or any other file
>          indirectly affecting the aspect of the manual.  The spurious
>          call might also be the consequence of using a buggy `make' (AIX,
>          DU, IRIX).  You might want to install the `Texinfo' package or
>          the `GNU make' package.  Grab either from any GNU archive site.

Install Texinfo 4.7 or later before running configure, or run
"contrib/gcc_update --touch" after unpacking the tar file.

> i'm not a programmer and i'm out of clue right now, anyone please help me ?

The truth is that building GCC yourself is a job for a programmer.
GCC 4.1 is very old.  You can probably find an installable package for
it on the net somewhere.

Ian

  reply	other threads:[~2012-11-21  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPiRsUXtWAHWDsLx0c8uNkDQV0drhShQRFziFy-isges6fy8gg@mail.gmail.com>
2012-11-21  6:23 ` Han Jiang
2012-11-21  6:41   ` Ian Lance Taylor [this message]
2012-11-21 16:40     ` Han Jiang
2012-11-21  6:29 ` Han Jiang
2012-11-21  6:38   ` Han Jiang

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=CAKOQZ8yF6hNanErUonvmAmA9yH89tgxY6iEAODQt5GYDG+DLww@mail.gmail.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=oglops@gmail.com \
    /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).