* 2.6.38-rc8 build failure - bridge vs. ipv6
@ 2011-03-10 10:07 Patrick Schaaf
0 siblings, 0 replies; 2+ messages in thread
From: Patrick Schaaf @ 2011-03-10 10:07 UTC (permalink / raw)
To: netdev; +Cc: davem
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* 2.6.38-rc8 build failure - bridge vs. ipv6
@ 2011-03-10 10:19 Patrick Schaaf
0 siblings, 0 replies; 2+ messages in thread
From: Patrick Schaaf @ 2011-03-10 10:19 UTC (permalink / raw)
To: netdev; +Cc: davem
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-03-10 10:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-10 10:07 2.6.38-rc8 build failure - bridge vs. ipv6 Patrick Schaaf
-- strict thread matches above, loose matches on Subject: below --
2011-03-10 10:19 Patrick Schaaf
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).