From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: jim.epost@gmail.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
bridge@lists.linux-foundation.org, kyeyoonp@codeaurora.org
Subject: Re: randconfig build error with next-20141028, in net/bridge
Date: Thu, 30 Oct 2014 15:36:50 -0400 (EDT) [thread overview]
Message-ID: <20141030.153650.2021747141086689600.davem@davemloft.net> (raw)
In-Reply-To: <20141030101708.12113903@urahara>
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.
prev parent reply other threads:[~2014-10-30 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 14:52 Jim Davis
2014-10-29 19:37 ` David Miller
2014-10-30 17:17 ` Stephen Hemminger
2014-10-30 19:36 ` David Miller [this message]
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=20141030.153650.2021747141086689600.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=jim.epost@gmail.com \
--cc=kyeyoonp@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stephen@networkplumber.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®