public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bill McEnaney" <bill@rkirkpat.net>
To: gcc-help@gcc.gnu.org
Subject: Building gcc-4.1.1
Date: Mon, 03 Jul 2006 01:02:00 -0000	[thread overview]
Message-ID: <20060703010210.5B55471AC1@saratoga.rkirkpat.net> (raw)

Hi, Folks,

You maybe remember that in another e-mail, I told you that my Sunblade
100 workstation keeps makeinfo in /usr/local/bin, gmake still insists
that makeinfo is missing from my system.  Here's the message I got when
I tried to rebuild gcc-4.1.1 earlier tonight.  Does the message help?

Thanks.

Bill

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.
gmake[3]: *** [fastjar.info] Error 1
gmake[3]: Leaving directory `/usr/share/src/gccobj/fastjar'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/usr/share/src/gccobj/fastjar'
gmake[1]: *** [all-fastjar] Error 2
gmake[1]: Leaving directory `/usr/share/src/gccobj'
gmake: *** [all] Error 2

________________________________________________________________
"Pro-choice?"  Then click here.
http://cathinsight.com/morality/saying.htm

             reply	other threads:[~2006-07-03  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  1:02 Bill McEnaney [this message]
2006-07-03  3:47 ` Ian Lance Taylor
2006-07-03  5:42 Bill McEnaney
2006-07-03  5:46 ` Ian Lance Taylor
2006-07-03  6:35 Bill McEnaney
2006-07-03  6:38 Bill McEnaney
2006-07-03  7:03 Bill McEnaney
2006-07-03 17:58 Bill McEnaney

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=20060703010210.5B55471AC1@saratoga.rkirkpat.net \
    --to=bill@rkirkpat.net \
    --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).