From: Pavel Machek <pavel@ucw.cz>
To: pablo@netfilter.org, kadlec@blackhole.kfki.hu, fw@strlen.de,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
kernel list <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au
Subject: Next 20190620: fails to compile in netfilter on x86-32
Date: Fri, 21 Jun 2019 13:03:11 +0200 [thread overview]
Message-ID: <20190621110311.GF24145@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Hi!
I get this during compilation:
CC net/netfilter/core.o
In file included from net/netfilter/core.c:19:0:
./include/linux/netfilter_ipv6.h: In function
‘nf_ipv6_cookie_init_sequence’:
./include/linux/netfilter_ipv6.h:174:2: error: implicit declaration
of function ‘__cookie_v6_init_sequence’
[-Werror=implicit-function-declaration]
return __cookie_v6_init_sequence(iph, th, mssp);
^
./include/linux/netfilter_ipv6.h: In function
‘nf_cookie_v6_check’:
./include/linux/netfilter_ipv6.h:189:2: error: implicit declaration
of function ‘__cookie_v6_check’
[-Werror=implicit-function-declaration]
return __cookie_v6_check(iph, th, cookie);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:278: recipe for target
'net/netfilter/core.o' failed
make[2]: *** [net/netfilter/core.o] Error 1
scripts/Makefile.build:498: recipe for target 'net/netfilter' failed
make[1]: *** [net/netfilter] Error 2
Is it known?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2019-06-21 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:03 Pavel Machek [this message]
2019-06-21 11:46 ` Next 20190620: fails to compile in netfilter on x86-32 Stephen Rothwell
2019-06-22 17:49 ` Next 20190621: fails to link f2fs in x86-32 Pavel Machek
2019-06-22 17:51 ` Pavel Machek
2019-06-24 0:20 ` Stephen Rothwell
2019-06-28 10:10 ` Pavel Machek
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=20190621110311.GF24145@amd \
--to=pavel@ucw.cz \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sfr@canb.auug.org.au \
/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.