From: Jeroen Vreeken <pe1rxq@amsat.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: sparse and mips
Date: Mon, 28 Feb 2005 15:00:44 +0100 [thread overview]
Message-ID: <4223240C.4010207@amsat.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0502281325390.5171@numbat.sonytel.be>
Geert Uytterhoeven wrote:
>You're using 2.6.10?
>
>When I played with sparse on m68k (cross-compile environment), I had to make
>some modifications to arch/m68k/Makefile, to pass a few additional flags to
>sparse in case of cross-compilation. Later these changes were moved to the main
>Makefile, since they were valid for all architectures if cross-compilation was
>involved.
>
>So I suggest to take a look at CHECKFLAGS in the main Makefile of the latest
>version (2.6.11-rc5) first, and see whether it works there.
>
>
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
else
CHECKFLAGS += -D_MIPS_SZLONG=64
endif
ifdef CONFIG_CPU_LITTLE_ENDIAN
CHECKFLAGS += -D__MIPSEL__
else
CHECKFLAGS += -D__MIPSEB__
endif
Jeroen
next prev parent reply other threads:[~2005-02-28 14:00 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 [this message]
2005-03-03 10:46 ` Ralf Baechle
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=4223240C.4010207@amsat.org \
--to=pe1rxq@amsat.org \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.