linux-kernel - Re: parisc arch makefile clean-up needed [Was: cleaning up "make headers

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]

Message-ID: <20071010204139.GA3255@uranus.ravnborg.org>
Date:	Wed, 10 Oct 2007 22:41:39 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Matthew Wilcox <matthew@....cx>
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]

> 
> 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?

Good question...
I prefer the solution used by powerpc.
See the checkbin dependency of archprepare:

archprepare: is only triggered when we actually try to build a kernel,
and will not trigger for the said headers_install thing.

	Sam
-
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/