public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Fedin Pavel <p.fedin@samsung.com>
Cc: insight@sourceware.org
Subject: Re: Problem building Insight
Date: Thu, 16 May 2013 15:50:00 -0000	[thread overview]
Message-ID: <51950059.2030105@redhat.com> (raw)
In-Reply-To: <001501ce5209$77fc2680$67f47380$%fedin@samsung.com>

On 05/16/2013 12:46 AM, Fedin Pavel wrote:
>   And one more such problem:

Yup. I have patches for two build errors those coming.
Problem is there is another upstream bug in gdb that prevents insight 
from running.

I should have this all sorted out later today.

Thank you for bringing this to my attention, though. I've been so busy, 
I could easily have not noticed for weeks!

Keith

      reply	other threads:[~2013-05-16 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  7:28 Fedin Pavel
2013-05-16  7:46 ` Fedin Pavel
2013-05-16 15:50   ` Keith Seitz [this message]

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=51950059.2030105@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sourceware.org \
    --cc=p.fedin@samsung.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).