linux-kernel - [REGRESSEION] x86: allyesconfig fails with 'debug' symbol

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

Date:	Sat, 26 Apr 2008 15:38:40 +0400
From:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>
To:	Linux-kernel <linux-kernel@...r.kernel.org>
CC:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>, thomas@...ischhofer.net
Subject: [REGRESSEION] x86: allyesconfig fails with 'debug' symbol

Hi,

The last commit as of writing this regression report is
b1721d0da266b4af8cb4419473b4ca36206ab200, and I'm using Linus tree.

The allyesconfig build fails with the following error:

[dmitri.vorobiev@...er linux-2.6]$ make ARCH=i386 CROSS_COMPILE=i386-linux-gnu- 

[ ... skipped ... ]

  LD      vmlinux.o
drivers/built-in.o: In function `SiS_EnableBridge':
/home/dmitri.vorobiev/Projects/misc/zoo/src/linux-2.6/drivers/video/sis/init301.c:4352: multiple definition of `debug'
arch/x86/kernel/built-in.o:/home/dmitri.vorobiev/Projects/misc/zoo/src/linux-2.6/arch/x86/kernel/entry_32.S:766: first defined here
i386-linux-gnu-ld: Warning: size of symbol `debug' changed from 76 in arch/x86/kernel/built-in.o to 4 in drivers/built-in.o
make: *** [vmlinux.o] Error 1
[dmitri.vorobiev@...er linux-2.6]$

Although it is obvious what causes this problem, just now I have no time
to try to resolve this, so I decided to just report the failure.

Thanks,
Dmitri
--
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/