From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: insight@sources.redhat.com, Keith Seitz <keiths@redhat.com>,
Andrew Cagney <ac131313@ges.redhat.com>
Subject: Re: [patch] a few more frame_in_dummy's
Date: Fri, 15 Nov 2002 13:04:00 -0000 [thread overview]
Message-ID: <3DD5614C.5000302@redhat.com> (raw)
In-Reply-To: <ro1ptt6prtv.fsf@jackfruit.Stanford.EDU>
> 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.
The configury assumes that you want to build everything in your tree (if
insight is present, then insight). You can disable this (from memory)
by configuring with --disable-gdbtk.
Andrew
prev parent reply other threads:[~2002-11-15 21:04 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
2002-11-15 13:04 ` Andrew Cagney [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=3DD5614C.5000302@redhat.com \
--to=ac131313@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=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).