From: Keith Owens <kaos@sgi.com>
To: "Michael Anburaj" <michaelanburaj@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linux for MIPS Atlas 4Kc board -problems :(
Date: Fri, 02 May 2003 15:22:13 +1000 [thread overview]
Message-ID: <9709.1051852933@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 01 May 2003 22:07:32 MST." <BAY1-F99BGpEI2rV4Zn000015fa@hotmail.com>
On Thu, 01 May 2003 22:07:32 -0700,
"Michael Anburaj" <michaelanburaj@hotmail.com> wrote:
>I did try that too...
>
>[root@localhost linux]# make ARCH=mips
>make -f scripts/Makefile.build obj=arch/mips/kernel
>arch/mips/kernel/offset.s
> gcc -Wp,-MD,arch/mips/kernel/.offset.s.d -D__KERNEL__ -Iinclude -Wall
>-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
>-fno-strict-aliasing -fno-common -I /usr/src/linux/include/asm/gcc -G 0
>-mno-abicalls -fno-pic -pipe -mcpu=r4600 -mips2 -Wa,--trap -nostdinc
>-iwithprefix include -DKBUILD_BASENAME=offset -S -o
>arch/mips/kernel/offset.s arch/mips/kernel/offset.c
>gcc: cannot specify -o with -c or -S and multiple compilations
>make[1]: *** [arch/mips/kernel/offset.s] Error 1
>make: *** [arch/mips/kernel/offset.s] Error 2
Because you mentioned Redhat 9, I have to assume that you are cross
compiling from i386 to mips, is that correct? If so, you need make
ARCH=mips and you have to specify the cross compile tools as well,
something like this :-
make ARCH=mips CROSS_COMPILE=/usr/bin/mips-linux- ...
If you are doing a native mips compile then the problem is that your
version of gcc does not like one or more of the command options, the
unknown option is being treated as a filename.
next prev parent reply other threads:[~2003-05-02 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 5:07 Linux for MIPS Atlas 4Kc board -problems :( Michael Anburaj
2003-05-02 5:22 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-15 6:24 Michael Anburaj
2003-05-03 9:05 Michael Anburaj
2003-05-03 2:54 Michael Anburaj
2003-05-03 2:36 Michael Anburaj
2003-05-02 6:47 Michael Anburaj
2003-05-02 3:25 Michael Anburaj
2003-05-02 4:18 ` Keith Owens
2003-05-03 1:09 ` 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=9709.1051852933@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-mips@linux-mips.org \
--cc=michaelanburaj@hotmail.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 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.