linux-kernel - Re: build issue #509 for v2.6.26-rc4-27-g0a2ce2f :undefined reference to `xquad

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]

Message-ID: <Pine.LNX.4.64.0805291219040.7193@shark.he.net>
Date:	Thu, 29 May 2008 12:21:19 -0700 (PDT)
From:	"Randy.Dunlap" <rdunlap@...otime.net>
To:	Toralf Förster <toralf.foerster@....de>
cc:	linux-kernel@...r.kernel.org
Subject: Re: build issue #509 for v2.6.26-rc4-27-g0a2ce2f :undefined reference
 to `xquad_portio'

On Thu, 29 May 2008, Toralf Förster wrote:

> Hello,
> 
> the build (.config attached) failed, make ends with :
> ...
>   CC      arch/x86/lib/usercopy_32.o
>   AR      arch/x86/lib/lib.a
>   LD      vmlinux.o
>   MODPOST vmlinux.o
> WARNING: modpost: Found 4 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> arch/x86/kernel/built-in.o: In function `setup_portio_remap':
> /home/tfoerste/devel/linux-2.6/include/asm-x86/mach-numaq/mach_apic.h:132: undefined reference to `xquad_portio'
> arch/x86/kernel/built-in.o: In function `MP_bus_info':
> /home/tfoerste/devel/linux-2.6/arch/x86/kernel/mpparse.c:114: undefined reference to `mpc_oem_bus_info'
> /home/tfoerste/devel/linux-2.6/arch/x86/kernel/mpparse.c:135: undefined reference to `mpc_oem_pci_bus'
> make: *** [.tmp_vmlinux1] Error 1
> 
> The build was made with :
> $>make randconfig; make clean; make
> 
> Here's the config:

[snip]

Yes, this is a longstanding build problem.  There was some
discussion about removing NUMAQ support from the kernel since the
machines are probably gone or dead, but I suppose that there was
no decision...

-- 
~Randy