From: Ramaraju G <ramaraju.g@nxp.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "insight@sourceware.org" <insight@sourceware.org>
Subject: RE: problem in building Insight debugger
Date: Mon, 20 Jul 2009 05:29:00 -0000 [thread overview]
Message-ID: <E0327731FC899B4D92EBF26CEF2A6B2116267E80CB@EU1RDCRDC1WX029.exi.nxp.com> (raw)
In-Reply-To: <4A60E5AE.7020809@redhat.com>
Yes, Keith, After installing the texinfo and GNU make, my build is through.
thanks
-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com]
Sent: 2009 Jul 18 2:27 AM
To: Ramaraju G
Cc: insight@sourceware.org
Subject: Re: problem in building Insight debugger
On 07/17/2009 12:40 PM, Keith Seitz wrote:
> You haven't left me enough of the build output to actually see the error...
Cincidentally enough, I just ran into this on my own, newly installed
Fedora 11 system. I think this is probably your problem:
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]: *** [bfd.info] Error 1
As the warning suggests, you must have the texinfo package installed.
This is required to build a snapshot.
If this isn't the problem you have afterall, then you must send the
actual error message.
Keith
next prev parent reply other threads:[~2009-07-20 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 10:52 Facing a malformed packet error using " Insightuser
2009-07-06 15:47 ` Keith Seitz
2009-07-07 5:39 ` Insightuser
2009-07-17 6:10 ` problem in building " Ramaraju G
2009-07-17 19:40 ` Keith Seitz
2009-07-17 20:57 ` Keith Seitz
2009-07-20 5:29 ` Ramaraju G [this message]
2009-07-20 7:16 ` Ramaraju G
2009-07-20 16:24 ` Keith Seitz
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=E0327731FC899B4D92EBF26CEF2A6B2116267E80CB@EU1RDCRDC1WX029.exi.nxp.com \
--to=ramaraju.g@nxp.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.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).