From: Keith Seitz <keiths@redhat.com>
To: RAYAPROL Raja <Raja.RAYAPROL@swift.com>
Cc: "insight@sourceware.org" <insight@sourceware.org>
Subject: Re: cannot build on RHEL 6
Date: Thu, 06 Sep 2012 18:08:00 -0000 [thread overview]
Message-ID: <5048E696.4000005@redhat.com> (raw)
In-Reply-To: <514883D0F12DEF4788558064C95ECAA332B2B0CA57@BE-EXCHANGE-09.swift.corp>
On 09/06/2012 10:56 AM, RAYAPROL Raja wrote:
> Thanks for the tip. I assumed that I was picking the stable branch.
Yeah, I apologize. I haven't actually made an official release in a long
time. I'm *long* overdue.
> I can't use cvs, but I tried to download the 7.0.5 sources.
Ick. 7.0.5 is still just as equally old. If you can download source
tarballs, here's what I would do:
Download the official 7.5 gdb release. Ping me, and I will send you the
insight bits (and instructions) for that release. This will give you
nearly a 7.5 release of Insight.
> [...] but I don't see a insight executable and gdb doesn't
> recognize the insight option.
Your build is messed up: insight was never built. Hmm. The file
"make.out.txt" doesn't even mention the gdb directory...
The MAKEINFO problem can be worked around by setting MAKEINFO=true in
your environment.
> Do you think you can help?
I hope so! :-)
Keith
next prev parent reply other threads:[~2012-09-06 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B3152C6-06A1-46FF-9A3F-444A16935920@hp.com>
2012-09-05 19:15 ` RAYAPROL Raja
2012-09-05 19:26 ` Keith Seitz
2012-09-05 19:44 ` RAYAPROL Raja
2012-09-05 20:18 ` Carl Lowenstein
2012-09-05 20:22 ` RAYAPROL Raja
2012-09-05 20:26 ` Keith Seitz
2012-09-06 17:57 ` RAYAPROL Raja
2012-09-06 18:08 ` Keith Seitz [this message]
2012-09-07 13:56 ` RAYAPROL Raja
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=5048E696.4000005@redhat.com \
--to=keiths@redhat.com \
--cc=Raja.RAYAPROL@swift.com \
--cc=insight@sourceware.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).