linux-kernel - Re: build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 9 May 2008 18:16:42 +0800
From:	WANG Cong <xiyou.wangcong@...il.com>
To:	toralf.foerster@....de
Cc:	WANG Cong <xiyou.wangcong@...il.com>,
	James.Bottomley@...senpartnership.com, linux-kernel@...r.kernel.org
Subject: Re: build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager:
	multiple definition of `phys_cpu_present_map'

On Fri, May 09, 2008 at 11:58:21AM +0200, =?ISO-8859-1?Q?Toralf_F=F6rster_ wrote:
>At Friday 09 May 2008 11:30:17 WANG Cong wrote :
>> On Fri, May 09, 2008 at 11:13:57AM +0200, =?ISO-8859-1?Q?Toralf_F=F6rster_ wrote:
>> >Hello,
>> >
>> >the build (.config attached) failed, make ends with :
>> >...
>> >  AR      arch/x86/lib/lib.a
>> >  LD      vmlinux.o
>> >arch/x86/mach-voyager/built-in.o:(.bss+0x2c): multiple definition of `phys_cpu_present_map'
>> >arch/x86/kernel/built-in.o:(.bss+0x200): first defined here
>> >ld: Warning: size of symbol `phys_cpu_present_map' changed from 32 in arch/x86/kernel/built-in.o to 4 in arch/x86/mach-voyager/built-in.o
>> >make: *** [vmlinux.o] Error 1
>> 
>> Could you please try my quick patch below?
>> 
>yep, that issue is fixed :-)
>

Thanks for your test!

That was a wrong fix, although it looks like passing compile test.
Please try the new one instead. ;-)


-- 
Hi, I'm a .signature virus, please copy/paste me to help me spread
all over the world.
--
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/