Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Modify gdb/Makefile.in to build observer.c
Date: Fri, 28 Feb 2003 15:19:00 -0000	[thread overview]
Message-ID: <20030228151904.GA23109@nevyn.them.org> (raw)
In-Reply-To: <20030228073413.GE6112@gnat.com>

On Thu, Feb 27, 2003 at 11:34:13PM -0800, Joel Brobecker wrote:
> I made the following changes in order to have observer.[hc] built
> in GDB. 
> 
> Since this unit is currently unused in GDB, I have considered not
> linking in this observer.o. However, I think I've seen another recent
> patch that is just about ready to benefit from this framework. So I
> discarded this idea.
> 
> There is one variable that I don't quite understand; it's
> HFILES_NO_SRCDIR. The comment ("Header files that need to have srcdir
> added", sic) did not help me, so I wasn't sure that observer.h does
> not need to be added to this list. Let me know if it should.

HFILES_NO_SRCDIR is only used for make TAGS, and that's been neglected
for a while now - I'd say, don't worry about it.

> 2003-02-27  J. Brobecker  <brobecker@gnat.com>
> 
>         * Makefile.in: Add rules to build and link in observer.o.
> 
> Ok to apply?

Since Andrew's already indicated he wants this linked in, and since I
actually have another bug that this will make much easier to solve,
please go ahead.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-28 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28  7:34 Joel Brobecker
2003-02-28 15:19 ` Daniel Jacobowitz [this message]
2003-02-28 17:14   ` Joel Brobecker

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=20030228151904.GA23109@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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