From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Get make TAGS to work in gdb directory
Date: Mon, 26 Sep 2005 01:39:00 -0000 [thread overview]
Message-ID: <20050926013855.GD22284@nevyn.them.org> (raw)
In-Reply-To: <17200.36038.631429.268643@farnswood.snap.net.nz>
On Wed, Sep 21, 2005 at 10:27:18AM +1200, Nick Roberts wrote:
>
> make TAGS doesn't seem to work in the gdb directory for two reason:
>
> 1) minimon.h, symfile-mem.h, amdfbsd-nat.c, irix4-nat.c, m3-nat.c,
> mipsm3-nat.c, ns32k-tdep.c, symm-tdep.c and symm-nat.c have been removed.
>
> 2) It doesn't find mi-*.c tui-*.c because they are in different
> directories.
>
>
> It's been bust for quite a long time so either people don't use it much,
> they have a local patch or there's something wrong with my setup. Assuming
> its not the latter, I attach a patch.
It's the first option, I think. I know I don't use it.
> 2005-09-21 Nick Roberts <nickrob@snap.net.nz>
>
> * Makefile.in (HFILES_NO_SRCDIR): Remove minimon.h, symfile-mem.h,
> amdfbsd-nat.c, irix4-nat.c, m3-nat.c, mipsm3-nat.c, ns32k-tdep.c,
> symm-tdep.c and symm-nat.c.
> (TAGFILES_NO_SRCDIR): Add SUBDIR_MI_SRCS SUBDIR_TUI_SRCS.
> (DEPFILES): Remove CONFIG_OBS and include it explicitly where needed.
This doesn't match what you said above but tipped me off to the
problem; s/amdfbsd-nat.c/amd64fbsd-nat.c/ instead please.
Also, removing CONFIG_OBS doesn't have quite the affect you wanted.
You've also lost anything else that configure can add e.g.
libunwind-frame.c. Would adding CONFIG_SRCS to TAGFILES_NO_SRCDIR
instead work?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-26 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 22:27 Nick Roberts
2005-09-21 14:36 ` Kris Warkentin
2005-09-28 3:23 ` Nick Roberts
2005-09-26 1:39 ` Daniel Jacobowitz [this message]
2005-09-26 4:43 ` Nick Roberts
2005-09-26 13:25 ` Daniel Jacobowitz
2005-09-28 3:01 ` Nick Roberts
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=20050926013855.GD22284@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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