Linux Ethernet Bridging - Oct 2014 - [Bridge] randconfig build error with next-20141028, in net/bridge

From: Jim Davis <jim.epost at gmail.com>
Date: Tue, 28 Oct 2014 07:52:47 -0700
> Building with the attached random configuration file,
> 
> net/built-in.o: In function `br_handle_frame_finish':
> (.text+0x40edf): undefined reference to `arp_tbl'
> net/built-in.o: In function `br_handle_frame_finish':
> (.text+0x40f3a): undefined reference to `arp_send'
> make: *** [vmlinux] Error 1
Kyeyoon-ssi, you will need to do something about this.

Your choices are either selecting INET (and thus also
CRYPTO and CRYPTO_AES, since INET needs those in order
to build properly), making bridging depeng on INET,
or protecting the new proxy-arp code with INET ifdef
checks.

On Wed, 29 Oct 2014 15:37:45 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Jim Davis <jim.epost@gmail.com>
> Date: Tue, 28 Oct 2014 07:52:47 -0700
> 
> > Building with the attached random configuration file,
> > 
> > net/built-in.o: In function `br_handle_frame_finish':
> > (.text+0x40edf): undefined reference to `arp_tbl'
> > net/built-in.o: In function `br_handle_frame_finish':
> > (.text+0x40f3a): undefined reference to `arp_send'
> > make: *** [vmlinux] Error 1
> 
> Kyeyoon-ssi, you will need to do something about this.
> 
> Your choices are either selecting INET (and thus also
> CRYPTO and CRYPTO_AES, since INET needs those in order
> to build properly), making bridging depeng on INET,
> or protecting the new proxy-arp code with INET ifdef
> checks.
Maybe make ARP proxy a config option under bridge and have
it depend on INET?

On Wed, 29 Oct 2014 15:37:45 -0400 (EDT)
David Miller <davem at davemloft.net> wrote:
> From: Jim Davis <jim.epost at gmail.com>
> Date: Tue, 28 Oct 2014 07:52:47 -0700
> 
> > Building with the attached random configuration file,
> > 
> > net/built-in.o: In function `br_handle_frame_finish':
> > (.text+0x40edf): undefined reference to `arp_tbl'
> > net/built-in.o: In function `br_handle_frame_finish':
> > (.text+0x40f3a): undefined reference to `arp_send'
> > make: *** [vmlinux] Error 1
> 
> Kyeyoon-ssi, you will need to do something about this.
> 
> Your choices are either selecting INET (and thus also
> CRYPTO and CRYPTO_AES, since INET needs those in order
> to build properly), making bridging depeng on INET,
> or protecting the new proxy-arp code with INET ifdef
> checks.
Maybe make ARP proxy a config option under bridge and have
it depend on INET?

From: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 30 Oct 2014 10:17:08 -0700
> On Wed, 29 Oct 2014 15:37:45 -0400 (EDT)
> David Miller <davem@davemloft.net> wrote:
> 
>> From: Jim Davis <jim.epost@gmail.com>
>> Date: Tue, 28 Oct 2014 07:52:47 -0700
>> 
>> > Building with the attached random configuration file,
>> > 
>> > net/built-in.o: In function `br_handle_frame_finish':
>> > (.text+0x40edf): undefined reference to `arp_tbl'
>> > net/built-in.o: In function `br_handle_frame_finish':
>> > (.text+0x40f3a): undefined reference to `arp_send'
>> > make: *** [vmlinux] Error 1
>> 
>> Kyeyoon-ssi, you will need to do something about this.
>> 
>> Your choices are either selecting INET (and thus also
>> CRYPTO and CRYPTO_AES, since INET needs those in order
>> to build properly), making bridging depeng on INET,
>> or protecting the new proxy-arp code with INET ifdef
>> checks.
> 
> Maybe make ARP proxy a config option under bridge and have
> it depend on INET?
I'd be fine with that too.