All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jeroen Vreeken <pe1rxq@amsat.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: sparse and mips
Date: Thu, 3 Mar 2005 10:46:54 +0000	[thread overview]
Message-ID: <20050303104654.GB5457@linux-mips.org> (raw)
In-Reply-To: <4223240C.4010207@amsat.org>

On Mon, Feb 28, 2005 at 03:00:44PM +0100, Jeroen Vreeken wrote:

> Adding the following few lines fixes the problems with the headers (they 
> are normally defined by gcc)...
> I am not sure that is all that is needed (the rest might just be me 
> doing bad things in my driver) but since they are mips specific I think 
> arch/mips/Makefile would be the right place for them:
> 
> CHECKFLAGS    += -D__mips__
> ifdef CONFIG_MIPS32
> CHECKFLAGS    += -D_MIPS_SZLONG=32

I went for something slightly more beautyful:

CHECKFLAGS-y                            += -D__linux__ -D__mips__
CHECKFLAGS-$(CONFIG_MIPS32)             += -D_MIPS_SZLONG=32 \
                                           -D__PTRDIFF_TYPE__=int
CHECKFLAGS-$(CONFIG_MIPS64)             += -D_MIPS_SZLONG=64 \
                                           -D__PTRDIFF_TYPE__="long int"
CHECKFLAGS-$(CONFIG_CPU_BIG_ENDIAN)     += -D__MIPSEL__
CHECKFLAGS-$(CONFIG_CPU_LITTLE_ENDIAN)  += -D__MIPSEL__

Still needs a few more symbols I guess.  And I fixed a few of the worst
offenders, especially uaccess.h.

  Ralf

  reply	other threads:[~2005-03-03 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 23:24 sparse and mips Jeroen Vreeken
2005-02-28 12:11 ` Ralf Baechle
2005-02-28 12:29   ` Geert Uytterhoeven
2005-02-28 14:00     ` Jeroen Vreeken
2005-03-03 10:46       ` Ralf Baechle [this message]
2005-03-03 11:38         ` Ulrich Eckhardt
2005-03-03 11:50           ` Ralf Baechle

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=20050303104654.GB5457@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pe1rxq@amsat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.