Browse Source

net: bridge builtin vs. ipv6 modular

When configs BRIDGE=y and IPV6=m, this build error occurs:

br_multicast.c:(.text+0xa3341): undefined reference to `ipv6_dev_get_saddr'

BRIDGE_IGMP_SNOOPING is boolean; if it were tristate, then adding
	depends on IPV6 || IPV6=n
to BRIDGE_IGMP_SNOOPING would be a good fix.  As it is currently,
making BRIDGE depend on the IPV6 config works.

Reported-by: Patrick Schaaf <netdev@bof.de>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Randy Dunlap 14 years ago
parent
commit
dcbcdf22f5
1 changed files with 1 additions and 0 deletions
  1. 1 0
      net/bridge/Kconfig

+ 1 - 0
net/bridge/Kconfig

@@ -6,6 +6,7 @@ config BRIDGE
 	tristate "802.1d Ethernet Bridging"
 	tristate "802.1d Ethernet Bridging"
 	select LLC
 	select LLC
 	select STP
 	select STP
+	depends on IPV6 || IPV6=n
 	---help---
 	---help---
 	  If you say Y here, then your Linux box will be able to act as an
 	  If you say Y here, then your Linux box will be able to act as an
 	  Ethernet bridge, which means that the different Ethernet segments it
 	  Ethernet bridge, which means that the different Ethernet segments it