From: Keith Seitz <keiths@redhat.com>
To: Ramaraju G <ramaraju.g@nxp.com>
Cc: "insight@sourceware.org" <insight@sourceware.org>
Subject: Re: problem in building Insight debugger
Date: Fri, 17 Jul 2009 19:40:00 -0000 [thread overview]
Message-ID: <4A60D3B3.4030007@redhat.com> (raw)
In-Reply-To: <E0327731FC899B4D92EBF26CEF2A6B21162673FA73@EU1RDCRDC1WX029.exi.nxp.com>
On 07/16/2009 11:09 PM, Ramaraju G wrote:
> config.status: creating po/Makefile.in
> config.status: executing depfiles commands
> config.status: executing libtool commands
> config.status: executing default-1 commands
> config.status: executing bfd_stdint.h commands
> config.status: executing default commands
> make[3]: Leaving directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/s
> rc/bfd/po'
> make[3]: Entering directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/
> src/bfd/po'
> make[3]: Nothing to be done for `info'.
> make[3]: Leaving directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/s
> rc/bfd/po'
> make[3]: Entering directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/
> src/bfd'
> make[3]: Nothing to be done for `info-am'.
> make[3]: Leaving directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/s
> rc/bfd'
> make[2]: *** [info-recursive] Error 1
> make[2]: Leaving directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/s
> rc/bfd'
> make[1]: *** [all-bfd] Error 2
> make[1]: Leaving directory `/cygdrive/o/space/__insight_MontaVistaMips32_Debug/s
> rc'
> make: *** [all] Error 2
You haven't left me enough of the build output to actually see the error...
Keith
next prev parent reply other threads:[~2009-07-17 19:40 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 [this message]
2009-07-17 20:57 ` Keith Seitz
2009-07-20 5:29 ` Ramaraju G
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=4A60D3B3.4030007@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=ramaraju.g@nxp.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).