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: <20071010202128.GG2730@parisc-linux.org> Date: Wed, 10 Oct 2007 14:21:28 -0600 From: Matthew Wilcox <matthew@....cx> To: Sam Ravnborg <sam@...nborg.org> Cc: "Robert P. J. Day" <rpjday@...dspring.com>, parisc-linux-request@...ts.parisc-linux.org, Randy Dunlap <randy.dunlap@...cle.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Grant Grundler <grundler@...isc-linux.org>, Kyle McMartin <kyle@...isc-linux.org> Subject: Re: parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures] On Wed, Oct 10, 2007 at 08:38:58PM +0200, Sam Ravnborg wrote: > parisc arch Makefile needs some love and care... None of your comments actually address the thing that he was having problems with: ifneq ($(call cc-ifversion, -lt, 0303, "bad"),) $(error Sorry, GCC v3.3 or above is required.) endif Now, compiler.h has some checks like: #elif __GNUC__ == 3 && __GNUC_MINOR__ >= 2 # include <linux/compiler-gcc3.h> #else # error Sorry, your compiler is too old/not recognized. #endif But it doesn't permit us to rule out gcc 3.3 unless we patch compiler.h. There's no asm/compiler.h, for example. Obviously, we could put some tests for compiler version in arch/parisc somewhere. Where's the right place these days? -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." - 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