From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: iptables -git automake warnings
Date: Mon, 12 Jan 2009 07:23:32 +0100 [thread overview]
Message-ID: <496AE1E4.9060508@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901120711210.21692@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Monday 2009-01-12 07:10, Patrick McHardy wrote:
>
>> Patrick McHardy wrote:
>>> Patrick McHardy wrote:
>>>> I get this with the current iptables -git version:
>>>>
>>>> Makefile.am:7: `:='-style assignments are not portable
>>>> Makefile.am:71: `:='-style assignments are not portable
>>>> Makefile.am:72: `:='-style assignments are not portable
>>>> Makefile.am:73: `:='-style assignments are not portable
>>>> Makefile.am:74: `:='-style assignments are not portable
>>>> Makefile.am:75: `:='-style assignments are not portable
>>>> Makefile.am:78: `:='-style assignments are not portable
>>>> Makefile.am:80: `:='-style assignments are not portable
>>>> Makefile.am:97: `%'-style pattern rules are a GNU make extension
>>> Additionally compilation aborts with:
>>>
>>> make[2]: *** No rule to make target
>>> `../include/linux/netfilter_ipv4/ipt_DSCP.h', needed by `libipt_ECN.oo'.
>>> Stop.
>> This is resolved by using a fresh clone.
>
> Must have been a really old tree, since no .c file besides
> libipt_DSCP.c (long renamed libxt_DSCP.c) ever used ipt_DSCP.h.
Possibly, I usually don't delete the tree. The error didn't happen
previously for some reason.
next prev parent reply other threads:[~2009-01-12 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 5:44 iptables -git automake warnings Patrick McHardy
2009-01-12 5:46 ` Patrick McHardy
2009-01-12 6:10 ` Jan Engelhardt
2009-01-12 6:22 ` Patrick McHardy
2009-01-12 6:10 ` Patrick McHardy
2009-01-12 6:13 ` Jan Engelhardt
2009-01-12 6:23 ` Patrick McHardy [this message]
2009-01-12 6:11 ` Jan Engelhardt
2009-01-12 6:22 ` Patrick McHardy
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=496AE1E4.9060508@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).