linux-mips
[Top] [All Lists]

Re: undefined reference to `__multi3' when building with gcc 7.x

To: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org, Waldemar Brodkorb <wbx@openadk.org>, James Hogan <james.hogan@mips.com>, Florian Fainelli <florian@openwrt.org>
Subject: Re: undefined reference to `__multi3' when building with gcc 7.x
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date: Sun, 3 Dec 2017 10:56:31 +0100
In-reply-to: <20170803225547.6caa602b@windsurf.lan>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
Organization: Free Electrons
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20170803225547.6caa602b@windsurf.lan>
Sender: linux-mips-bounce@linux-mips.org
Hello,

+James Hogan in Cc.

On Thu, 3 Aug 2017 22:55:47 +0200, Thomas Petazzoni wrote:

> When trying to build the current Linux master with a gcc 7.x toolchain
> for mips64r6-n32, I'm getting the following build failure:
> 
> crypto/scompress.o: In function `.L31':
> scompress.c:(.text+0x2a0): undefined reference to `__multi3'
> drivers/base/component.o: In function `.L97':
> component.c:(.text+0x4a4): undefined reference to `__multi3'
> drivers/base/component.o: In function `component_master_add_with_match':
> component.c:(.text+0x8c4): undefined reference to `__multi3'
> net/core/ethtool.o: In function `ethtool_set_per_queue_coalesce':
> ethtool.c:(.text+0x1ab0): undefined reference to `__multi3'
> Makefile:1000: recipe for target 'vmlinux' failed
> make[2]: *** [vmlinux] Error 1

I'm still facing this problem. There was a lengthy thread about it back
in August when I reported the problem, but then it calmed down, with no
real solution proposed.

Are there plans to fix this at some point?

Thanks a lot,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

<Prev in Thread] Current Thread [Next in Thread>