linux-kernel - Re: 3.7.0-rc4 build failure on alpha: MPILIB

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 11 Nov 2012 17:10:53 -0600
From:	Bob Tracy <rct@...rkin.frus.com>
To:	linux-kernel@...r.kernel.org
Cc:	mcree@...on.net.nz
Subject: Re: 3.7.0-rc4 build failure on alpha: MPILIB

On Mon, Nov 05, 2012 at 07:53:13AM -0600, Bob Tracy wrote:
> With digital signature verification support (SIGNATURE, MPILIB) enabled
> on the Alpha platform, I get the following during the MODPOST section of
> the build:
> 
> ERROR: "__udiv_qrnnd" [lib/mpi/mpi.ko] undefined!
> 
> Current compiler is gcc-4.6.3

Got a workaround.  I'll leave it to the "powers that be" for a proper
fix.  Issue is "__udiv_qrnnd" is part of "arch/alpha/math-emu" and is
built-in.  If MPILIB is built as a module, you get the undefined symbol
error.  If "CONFIG_MPILIB=y" (built-in), no undefined symbol issue.

My best guess is, the proper solution will involve either tightening the
configuration dependencies a bit, or making sure required symbols are
properly exported for use by modules.

-- 
------------------------------------------------------------------------
Bob Tracy          |  "Build a man a fire, he'll be warm for a day.  Set
rct@...s.com       |   a man on fire, he'll be warm for the rest of his
                   |   life."	-- David Burge (Iowahawk)
------------------------------------------------------------------------
--
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/