public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: [patch] a few more frame_in_dummy's
Date: Fri, 15 Nov 2002 11:28:00 -0000	[thread overview]
Message-ID: <ro1lm3upr84.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <Pine.LNX.4.44.0211151120120.1547-100000@valrhona.uglyboxes.com>

On Fri, 15 Nov 2002 11:22:17 -0800 (PST), Keith Seitz <keiths@redhat.com> said:
> On 15 Nov 2002, David Carlton wrote:

>> Incidentally, does core GDB really depend on the files in
>> SUBDIR_GDBTK_OBS?  If not, would it be possible to reorganize
>> Makefile.in to reflect that fact?  Because the way that I found those
>> frame_in_dummy problems was that I was trying to build GDB in a source
>> tree that included insight and where -Werror was turned on; it seems
>> to me unfortunate that I had to fix problems in insight before I could
>> get GDB to compile.

> I'm working on ripping everything Insight-related out of core
> gdb. I've submitted at least one RFC on how to complete this (one on
> init.c and one on options processing), but I haven't found the time
> to finish the work just yet. I seem to always get side-tracked by
> something.

Ah, I see.

> I'll see if I can't find some time next week to at least revisit
> some of this.

Thanks.  Though please don't hurry on my account: it's quite rare for
insight to cause problems when compiling GDB, and probably most such
issues will be as easily fixed as this one was.  (On the other hand,
if you're waiting for an excuse to get back to this, I'm happy to
provide one!)

David Carlton
carlton@math.stanford.edu

  reply	other threads:[~2002-11-15 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ro1heen3j0s.fsf@jackfruit.Stanford.EDU>
2002-11-12 12:24 ` Andrew Cagney
2002-11-15 11:15   ` David Carlton
2002-11-15 11:22     ` Keith Seitz
2002-11-15 11:28       ` David Carlton [this message]
2002-11-15 13:04     ` Andrew Cagney

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=ro1lm3upr84.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=insight@sources.redhat.com \
    --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).