From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: Build error v3.9-rc when CONFIG_IPV6 configured as module Date: Mon, 15 Apr 2013 11:02:15 +0200 Message-ID: <1366016535.8361.2.camel@jlt4.sipsolutions.net> References: (sfid-20130414_114618_800925_33CBD969) Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: davem@davemloft.net, netdev@vger.kernel.org To: Tomas Melin Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:48924 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933449Ab3DOJC0 (ORCPT ); Mon, 15 Apr 2013 05:02:26 -0400 In-Reply-To: (sfid-20130414_114618_800925_33CBD969) Sender: netdev-owner@vger.kernel.org List-ID: On Sun, 2013-04-14 at 12:45 +0300, Tomas Melin wrote: > It seems CONFIG_IPV6 cannot be built as a module, using "m"-option > leads to to the following linking error: > > net/built-in.o: In function `ieee80211_unregister_hw': > (.text+0x10f0e1): undefined reference to `unregister_inet6addr_notifier' > net/built-in.o: In function `ieee80211_register_hw': > (.text+0x10f610): undefined reference to `register_inet6addr_notifier' > make: *** [vmlinux] Error 1 > > This happens since the caller net/mac80211/main.c is statically built > in but net/ipv6/addrconf.c is then built as a module. Is this expected > behaviour or should it be fixed? > > Configuration: v3.9-rc6 with defconfig but ipv6 set to be a module > instead of built in. Oops, I didn't realize that IPv6 could even (still) be built as a module. I'll add this to mac80211's Kconfig: depends on IPV6 || !IPV6 to fix this. johannes