| 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
| ||
|
Message-ID: <20100817155333.GA17624@foursquare.net> Date: Tue, 17 Aug 2010 11:53:33 -0400 From: Chris Frey <cdfrey@...rsquare.net> To: Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org Subject: Re: compiler warnings in 2.6.35.2 On Tue, Aug 17, 2010 at 08:31:59AM +0200, Borislav Petkov wrote: > From: Chris Frey <cdfrey@...rsquare.net> > Date: Tue, Aug 17, 2010 at 02:28:01AM -0400 > > > > > CC mm/swap.o > > > > In file included from include/linux/kobject.h:21, > > > > from include/linux/sched.h:91, > > > > from mm/swap.c:17: > > > > include/linux/sysfs.h:183: warning: parameter has incomplete type > > > > /home/cdfrey/kernel/git/linux/arch/x86/include/asm/cpufeature.h: In function `__static_cpu_has': > > > > /home/cdfrey/kernel/git/linux/arch/x86/include/asm/cpufeature.h:315: warning: asm operand 1 probably doesn't match constraints > > > > > > Which compiler version are you using? > > > > GCC 3.3 > > Any chance to upgrade to a 4.x version? I could, but Documentation/Changes says gcc 3.2 is the minimum, so I hoped 3.3 would be sufficient. As for the first warning, doesn't it just need include/linux/kobject.h to be included for the enum type? As for the second warning, I'm not sure I even understand it. - Chris -- 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/
Powered by blists - more mailing lists