Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Let {TM,XM,NM}_FILE specify a path
Date: Fri, 03 Sep 2004 16:39:00 -0000	[thread overview]
Message-ID: <41389DFA.5020104@gnu.org> (raw)
In-Reply-To: <01c491a7$Blat.v2.2.2$8cce1ae0@zahav.net.il>

>>> Date: Thu, 02 Sep 2004 18:12:22 -0400
>>> From: Andrew Cagney <cagney@gnu.org>
>>> 
>>> Many of the still existing TM files (the others are done for 
>>> consistency) are just acting as an indirect include of another file. 
>>> For instance, tm-nbsd.h #includes "solib.h".  This patch tweaks 
>>> configure.in so that a TM_FILE can explicitly specify any file (instead 
>>> of having to pull it in via an #include) - that lets us eliminate both 
>>> the indirection and the unnecessary config file.
> 
> 
> Perhaps we should rename TM_FILE to something like TM_INCLUDE, then.

If you prefer, I can rename it to DEPRECATED_TM_INCLUDE when committing 
my pending deprecation patch.

> Btw, did we decide upon all these recent changes against *_FILE
> thingies?

Long long ago we decided that GDB would be strictly multi-arch, and 
hence that all tm-*.h files (and TM_FILE hackery) should be deleted. 
This deletes another 13 of those files.

If you prefer I can delete the tm-*.h files and TM_FILE configury outright.

Andrew



  reply	other threads:[~2004-09-03 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 22:13 Andrew Cagney
2004-09-03 11:17 ` Eli Zaretskii
2004-09-03 16:39   ` Andrew Cagney [this message]
2004-09-04 11:42     ` Eli Zaretskii
2004-09-09 15:17       ` Andrew Cagney
2004-09-09 19:19         ` Eli Zaretskii

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=41389DFA.5020104@gnu.org \
    --to=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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