From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Melin <tomas.melin@iki.fi>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: Build error v3.9-rc when CONFIG_IPV6 configured as module
Date: Mon, 15 Apr 2013 11:04:37 +0200 [thread overview]
Message-ID: <1366016677.8361.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1366016535.8361.2.camel@jlt4.sipsolutions.net>
On Mon, 2013-04-15 at 11:02 +0200, Johannes Berg wrote:
> 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.
Hm, actually, that's not sufficient since there are no no-op versions of
these functions when IPv6 isn't built ... needs a bit more.
johannes
next prev parent reply other threads:[~2013-04-15 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 9:45 Build error v3.9-rc when CONFIG_IPV6 configured as module Tomas Melin
2013-04-15 9:02 ` Johannes Berg
2013-04-15 9:04 ` Johannes Berg [this message]
2013-04-15 9:05 ` Johannes Berg
2013-04-15 17:30 ` David Miller
2013-04-15 18:12 ` Johannes Berg
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=1366016677.8361.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tomas.melin@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.