From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-decnet-user@lists.sourceforge.net,
Brian Vazquez <brianvv@google.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: Tree for Jul 31 (net/decnet/ & FIB_RULES)
Date: Sat, 1 Aug 2020 10:35:07 +1000 [thread overview]
Message-ID: <20200801103507.03ae069b@canb.auug.org.au> (raw)
In-Reply-To: <4c6abcd0-e51b-0cf3-92de-5538c366e685@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
Hi Randy,
On Fri, 31 Jul 2020 08:53:09 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> on i386:
>
> ld: net/core/fib_rules.o: in function `fib_rules_lookup':
> fib_rules.c:(.text+0x16b8): undefined reference to `fib4_rule_match'
> ld: fib_rules.c:(.text+0x16bf): undefined reference to `fib4_rule_match'
> ld: fib_rules.c:(.text+0x170d): undefined reference to `fib4_rule_action'
> ld: fib_rules.c:(.text+0x171e): undefined reference to `fib4_rule_action'
> ld: fib_rules.c:(.text+0x1751): undefined reference to `fib4_rule_suppress'
> ld: fib_rules.c:(.text+0x175d): undefined reference to `fib4_rule_suppress'
>
> CONFIG_DECNET=y
> CONFIG_DECNET_ROUTER=y
>
> DECNET_ROUTER selects FIB_RULES.
I assume that CONFIG_IP_MULTIPLE_TABLES was not set for that build?
Caused by commit
b9aaec8f0be5 ("fib: use indirect call wrappers in the most common fib_rules_ops")
from the net-next tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-01 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 11:19 linux-next: Tree for Jul 31 Stephen Rothwell
2020-07-31 15:53 ` linux-next: Tree for Jul 31 (net/decnet/ & FIB_RULES) Randy Dunlap
2020-08-01 0:35 ` Stephen Rothwell [this message]
2020-08-01 0:50 ` Randy Dunlap
2020-08-01 3:10 ` Brian Vazquez
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=20200801103507.03ae069b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).