From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Ramón Rey Vicente" <rrey@usuarios.retecal.es>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6-bk] net/core/sock.o build failed
Date: Thu, 30 Dec 2004 01:13:22 -0200 [thread overview]
Message-ID: <41D37252.8020201@conectiva.com.br> (raw)
In-Reply-To: <41D34E4D.7020802@usuarios.retecal.es>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Ramón Rey Vicente wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> CC net/core/sock.o
> In file included from include/net/ipv6.h:18,
> ~ from include/net/xfrm.h:16,
> ~ from net/core/sock.c:121:
> include/linux/ipv6.h: In function `inet6_sk':
> include/linux/ipv6.h:278: error: structure has no member named `pinet6'
> make[2]: *** [net/core/sock.o] Error 1
> make[1]: *** [net/core] Error 2
> make: *** [net] Error
Use the attached patch, this was already sent to David Miller, as I mentioned
in another message, this only happens when you don't select IPV6.
Regards,
- Arnaldo
[-- Attachment #2: inet6_sk.patch --]
[-- Type: text/plain, Size: 648 bytes --]
===== include/linux/ipv6.h 1.23 vs edited =====
--- 1.23/include/linux/ipv6.h 2004-12-27 23:56:33 -02:00
+++ edited/include/linux/ipv6.h 2004-12-29 20:22:45 -02:00
@@ -273,6 +273,7 @@
struct ipv6_pinfo inet6;
};
+#if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)
static inline struct ipv6_pinfo * inet6_sk(const struct sock *__sk)
{
return inet_sk(__sk)->pinet6;
@@ -283,7 +284,6 @@
return &((struct raw6_sock *)__sk)->raw6;
}
-#if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)
#define __ipv6_only_sock(sk) (inet6_sk(sk)->ipv6only)
#define ipv6_only_sock(sk) ((sk)->sk_family == PF_INET6 && __ipv6_only_sock(sk))
#else
next prev parent reply other threads:[~2004-12-30 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:39 [2.6-bk] net/core/sock.o build failed Ramón Rey Vicente
2004-12-30 3:13 ` Arnaldo Carvalho de Melo [this message]
2004-12-30 17:05 ` Ramón Rey Vicente
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=41D37252.8020201@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrey@usuarios.retecal.es \
/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