From: Ralf Baechle <ralf@linux-mips.org>
To: "Neeraj Garg, Noida" <ngarg@noida.hcltech.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linux-MIPS compilation
Date: Tue, 1 Apr 2003 13:42:58 +0200 [thread overview]
Message-ID: <20030401134258.A7618@linux-mips.org> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB2121086ED859@exch-01.noida.hcltech.com>; from ngarg@noida.hcltech.com on Tue, Apr 01, 2003 at 12:05:18PM +0530
On Tue, Apr 01, 2003 at 12:05:18PM +0530, Neeraj Garg, Noida wrote:
> Using compilation options:
> mips-linux-gcc -D__KERNEL__ -D__linux__ -D_MIPS_SZLONG=32
> -I/usr/emb_linux/linux-2.4.20/include -D__linux__ -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I
> /usr/emb_linux/linux-2.4.20/include/asm/gcc -G 0 -mno-abicalls -fno-pic
> -pipe -g -mcpu=r4600 -mips2 -Wa,--trap -DUTS_MACHINE='"mips"'
>
> I have got a tons of warnings named as:
> {standard input}: Assembler messages:
> {standard input}:784: Warning: Macro instruction expanded into multiple
> instructions
> {standard input}:784: Warning: No .cprestore pseudo-op used in PIC code
>
> Can anybody help out to remove these warnings?
The options -D__linux__ -D_MIPS_SZLONG=32 and the error messages make it
look like you're forcing a non-Linux toolchain into building a kernel.
Ralf
next prev parent reply other threads:[~2003-04-01 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 6:35 Linux-MIPS compilation Neeraj Garg, Noida
2003-04-01 11:42 ` Ralf Baechle [this message]
2003-04-01 13:57 ` Brian Murphy
2003-04-01 14:03 ` Ralf Baechle
2003-04-01 14:58 ` Geert Uytterhoeven
2003-04-01 15:25 ` 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=20030401134258.A7618@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ngarg@noida.hcltech.com \
/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