public inbox for
help / color / mirror / Atom feed
From: Keith Seitz <>
Subject: Re: insight/282: insight Can't compile insight
Date: Sat, 19 Nov 2005 19:43:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

The following reply was made to PR insight/282; it has been noted by GNATS.

From: Keith Seitz <>
Subject: Re: insight/282: insight Can't compile insight
Date: Sat, 19 Nov 2005 11:39:03 -0800

 Michael Stather wrote:
 > I don´t know how I can send a file to the bug (if not even reponsing works
 > correctly, but thanks for fixing this)
 > so I attach it here. 
  From your build.out file:
 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.
 make[2]: *** [../../../src/bfd/doc/] Fehler 1
 Do you have the texinfo package installed? (Is /usr/bin/makeinfo available?)
 Alternatively, you could simply barge past this error by using "make 
 -k". Of course, that could make other errors more difficult to find.

             reply	other threads:[~2005-11-19 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 19:43 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-19 18:23 Michael Stather
2005-11-19 18:13 Keith Seitz
2005-11-19 16:30 kseitz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).