From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] build: have `make clean` remove dep files too
Date: Mon, 10 Sep 2012 15:44:13 +0200 [thread overview]
Message-ID: <20120910134413.GA23537@1984> (raw)
In-Reply-To: <1347282605-20781-1-git-send-email-jengelh@inai.de>
On Mon, Sep 10, 2012 at 03:10:05PM +0200, Jan Engelhardt wrote:
> While changing branches, one can hit errors like:
>
> make[2]: *** CC libipt_CLUSTERIP.oo
> No hay ninguna regla para construir el objetivo
> `../include/net/netfilter/nf_nat.h', necesario para
> `libipt_DNAT.oo'. Alto.
>
> Pablo thinks dep files should be removed on `make clean`, and I
> concur. (JFI, Note that native automake would not clear its ".deps"
> directory.) Keep the "distclean: clean" line to keep invocations by
> automake from the parent directory working.
As soon as I get it fixed for me is fine, I have applied this patch.
prev parent reply other threads:[~2012-09-10 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 10:28 [PATCH] build: make clean removes .*.d and *.d pablo
2012-09-10 13:10 ` [PATCH] build: have `make clean` remove dep files too Jan Engelhardt
2012-09-10 13:44 ` Pablo Neira Ayuso [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=20120910134413.GA23537@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@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.