Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Fri, 31 Jul 2020 17:50:40 -0700
Message-ID: <97853126-c3fb-fced-547f-6dd7d5c89ca9@infradead.org> (raw)
In-Reply-To: <20200801103507.03ae069b@canb.auug.org.au>

On 7/31/20 5:35 PM, Stephen Rothwell wrote:
> 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?

Correct.

> Caused by commit
> 
>   b9aaec8f0be5 ("fib: use indirect call wrappers in the most common fib_rules_ops")
> 
> from the net-next tree.

thanks.

-- 
~Randy


  reply index

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
2020-08-01  0:50     ` Randy Dunlap [this message]
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=97853126-c3fb-fced-547f-6dd7d5c89ca9@infradead.org \
    --to=rdunlap@infradead.org \
    --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=sfr@canb.auug.org.au \
    /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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git