From: Patrick Schaaf <netdev@bof.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: 2.6.38-rc8 build failure - bridge vs. ipv6
Date: Thu, 10 Mar 2011 11:07:53 +0100 [thread overview]
Message-ID: <1299751673.4109.23.camel@lat1> (raw)
Hi all,
I see a build / link failure:
net/built-in.o: In function `br_ip6_multicast_alloc_query':
/usr/src/linux-2.6.38-rc8/net/bridge/br_multicast.c:448: undefined
reference to `ipv6_dev_get_saddr'
This happens with bridging build-in and ipv6 modular.
The call to ipv6_dev_get_saddr was introduced there between 2.6.38-rc6
and 2.6.38-rc8, the -rc6 built just fine with the same .config
I work around it by making bridge build modular, but you might want to
fix it properly before releasing 2.6.38.
best regards
Patrick
next reply other threads:[~2011-03-10 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 10:07 Patrick Schaaf [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-10 10:19 2.6.38-rc8 build failure - bridge vs. ipv6 Patrick Schaaf
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=1299751673.4109.23.camel@lat1 \
--to=netdev@bof.de \
--cc=davem@davemloft.net \
--cc=netdev@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).