public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Cedric Roux <cedric.roux@acri-st.fr>
Cc: Olumide <50295@web.de>, gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Wed, 19 Jan 2011 16:47:00 -0000	[thread overview]
Message-ID: <AANLkTik6QLVqqJfPaEXS8T9JNyfSbvohtfvxWedVcFai@mail.gmail.com> (raw)
In-Reply-To: <4D3714CB.7040302@acri-st.fr>

On 19 January 2011 16:43, Cedric Roux wrote:
> On 01/19/2011 05:37 PM, Olumide 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.
>
> try to start all over from scratch, you did a "make distclean" right?
> unzip the gcc tar.gz again and start from that clean point
> (just a guess, I had that error many times with many software out there
> because of a make distclean)
>

Also, it looks as though maybe you're building inside the gcc source tree:
/transfer/gcc412/gcc-4.1.2/build

Don't do that - the instructions you linked to correctly say to create
a directory next to the source tree and build in there.

  reply	other threads:[~2011-01-19 16:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51   ` Olumide
2011-01-19 16:21     ` Ian Lance Taylor
2011-01-19 16:37       ` Olumide
2011-01-19 16:39         ` Andrew Haley
2011-01-19 17:08           ` Olumide
2011-01-19 17:11             ` Andrew Haley
2011-01-19 20:13               ` Olumide
2011-01-19 21:51                 ` David Daney
2011-01-20 13:56                   ` Olumide
2011-01-20 17:23                     ` Olumide
2011-01-20 20:04                       ` Jonathan Wakely
2011-01-25 10:30                       ` Olumide
2011-01-25 10:59                         ` Jonathan Wakely
2011-01-25 11:34                           ` Olumide
2011-01-25 11:56                             ` Jonathan Wakely
2011-01-25 13:51                               ` Olumide
2011-01-25 10:59                         ` Kai Ruottu
2011-01-19 16:43         ` Cedric Roux
2011-01-19 16:47           ` Jonathan Wakely [this message]
2011-01-19 15:19 ` Jeff Law

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=AANLkTik6QLVqqJfPaEXS8T9JNyfSbvohtfvxWedVcFai@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=50295@web.de \
    --cc=cedric.roux@acri-st.fr \
    --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).