From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Sam Ravnborg <sam@ravnborg.org>,
parisc-linux-request@lists.parisc-linux.org,
Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Grant Grundler <grundler@parisc-linux.org>,
Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures]
Date: Wed, 10 Oct 2007 17:33:35 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710101729001.17053@localhost.localdomain> (raw)
In-Reply-To: <20071010202128.GG2730@parisc-linux.org>
On Wed, 10 Oct 2007, Matthew Wilcox wrote:
> 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.
hmmmm ... actually, there is ... sort of:
$ find include -name compiler.h
include/asm-alpha/compiler.h
include/asm-mips/compiler.h
include/linux/compiler.h
$ grep -r "asm/compiler.h" *
arch/mips/kernel/cpu-bugs64.c:#include <asm/compiler.h>
arch/mips/kernel/time.c:#include <asm/compiler.h>
arch/mips/au1000/common/time.c:#include <asm/compiler.h>
arch/alpha/kernel/sys_sio.c:#include <asm/compiler.h>
include/asm-alpha/mmu_context.h:#include <asm/compiler.h>
include/asm-alpha/core_marvel.h:#include <asm/compiler.h>
include/asm-alpha/core_t2.h:#include <asm/compiler.h>
... lots more alpha stuff ...
so there does appear to be some precedent for an asm/compiler.h.
for better or worse.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-10-10 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:44 cleaning up "make headers_install" for various architectures Robert P. J. Day
2007-10-10 16:59 ` Randy Dunlap
2007-10-10 17:26 ` Robert P. J. Day
2007-10-10 18:38 ` parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures] Sam Ravnborg
2007-10-10 19:38 ` Kyle McMartin
2007-10-10 19:58 ` Sam Ravnborg
2007-10-10 20:21 ` Matthew Wilcox
2007-10-10 20:41 ` Sam Ravnborg
2007-10-10 21:33 ` Robert P. J. Day [this message]
2007-10-10 19:15 [matthew@wil.cx: Re: [parisc-linux] parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures]] Matthew Wilcox
2007-10-10 19:54 ` parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures] Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0710101729001.17053@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=parisc-linux-request@lists.parisc-linux.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®