From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [PATCH] arch/ia64/tools/Makefile
Date: Fri, 26 Jul 2002 16:25:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905837@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905829@msgid-missing>
Shouldn't "mrproper" simply have a dependency on "clean"?
--david
>>>>> On Wed, 24 Jul 2002 07:20:08 -0700, "David N. Lombard" <david.lombard@mscsoftware.com> said:
David.L> sigh... The earlier arch/ia64/tools/Makefile patch
David.L> replicated the action for both targets -- a redundant
David.L> action.
David.L> Attached is the file I intended to send.
David.L> David N. Lombard wrote:
>> The arch/ia64/tools/Makefile has an empty action for the mrproper
>> target. The result is that arch/ia64/tools/print_offsets.s,
>> arch/ia64/tools/print_offsets, and arch/ia64/tools/offsets.h
>> remain after a "make mrproper". The files are deleted with "make
>> distclean".
>>
>> So, this could be a (subtle) intended difference between the
>> mrproper and distclean targets, but that seems unlikely.
>>
>> The attached patch moves the file deletion from the clean target
>> (invoked via distclean) to the mrproper target; the distclean
>> target still results in the files being deleted.
David.L> -- David N. Lombard MSC.Software ---
David.L> arch/ia64/tools/Makefile.orig Tue Jul 23 17:01:41 2002 +++
David.L> arch/ia64/tools/Makefile Tue Jul 23 17:01:55 2002 @@ -5,9
David.L> +5,9 @@ all:
David.L> mrproper: + rm -f print_offsets.s print_offsets offsets.h
David.L> clean: - rm -f print_offsets.s print_offsets offsets.h
David.L> fastdep: offsets.h @if ! cmp -s offsets.h ${TARGET}; then
David.L> \
prev parent reply other threads:[~2002-07-26 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 14:20 [Linux-ia64] Re: [PATCH] arch/ia64/tools/Makefile David N. Lombard
2002-07-26 16:25 ` David Mosberger [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=marc-linux-ia64-105590701905837@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.