[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20141030.153650.2021747141086689600.davem@davemloft.net>
Date: Thu, 30 Oct 2014 15:36:50 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: stephen@...workplumber.org
Cc: jim.epost@...il.com, sfr@...b.auug.org.au,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
bridge@...ts.linux-foundation.org, kyeyoonp@...eaurora.org
Subject: Re: randconfig build error with next-20141028, in net/bridge
From: Stephen Hemminger <stephen@...workplumber.org>
Date: Thu, 30 Oct 2014 10:17:08 -0700
> On Wed, 29 Oct 2014 15:37:45 -0400 (EDT)
> David Miller <davem@...emloft.net> wrote:
>
>> From: Jim Davis <jim.epost@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists