From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] Missing files in Makefile.in
Date: Fri, 25 Mar 2011 16:23:00 -0000 [thread overview]
Message-ID: <m3fwqbw5gk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <33303.1665221371$1301013974@news.gmane.org> (Pierre Muller's message of "Fri, 25 Mar 2011 01:45:52 +0100")
>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:
Pierre> List of not listed headers:
[...]
Pierre> List of not listed c sources:
[...]
I think headers and source files only really need to be listed for TAGS.
It would be great to list them all, though.
Pierre> I also noticed that there are
Pierre> files located in gdbserver subdirectory
Pierre> that are listed in this Makefile.in...
I don't know about this one. For TAGS it seems like the wrong thing;
gdbserver should have its own TAGS file.
Pierre> Should we do something about those
Pierre> inconsistencies?
Yes please :-)
It would be nice to move to a more Automake-like scheme, where the build
sources mention source files only, and then we use .c->.o substitutions
to list the object files. Or, we could just switch to Automake. Either
of these is likely to be a pain though; if you want to just patch up the
existing stuff, that is totally fine.
Tom
next parent reply other threads:[~2011-03-25 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33303.1665221371$1301013974@news.gmane.org>
2011-03-25 16:23 ` Tom Tromey [this message]
2011-03-29 16:00 ` [RFA] " Pierre Muller
[not found] ` <43141.6332409301$1301413721@news.gmane.org>
2011-03-29 20:01 ` Tom Tromey
2011-03-25 9:58 [RFC] " Pierre Muller
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=m3fwqbw5gk.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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