From: "H . J . Lu" <hjl@lucon.org>
To: Johannes Stezenbach <js@convergence.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: The Linux binutils 2.11.92.0.12 is released.
Date: Tue, 27 Nov 2001 10:25:50 -0800 [thread overview]
Message-ID: <20011127102550.A30681@lucon.org> (raw)
In-Reply-To: <20011127180022.A6897@convergence.de>; from js@convergence.de on Tue, Nov 27, 2001 at 06:00:22PM +0100
On Tue, Nov 27, 2001 at 06:00:22PM +0100, Johannes Stezenbach wrote:
>
> b) I still get the -march vs. -mipsN warings:
>
> mipsel-linux-gcc -I /home/js/MIPS/kernel/build/linux-2.4.14-mips/include/asm/gcc -D__KERNEL__ -I/home/js/MIPS/kernel/build/linux-2.4.14-mips/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -G 0 -mno-abicalls -fno-pic -mips2 -Wa,-m4100,--trap -pipe -fno-omit-frame-pointer -c -o sched.o sched.c
> Assembler messages:
> Warning: The -march option is incompatible to -mipsN and therefore ignored.
>
Please make sure binutils 2.11.92.0.12 is used. Please send me the
output of
# mipsel-linux-gcc -v -I /home/js/MIPS/kernel/build/linux-2.4.14-mips/include/asm/gcc -D__KERNEL__ -I/home/js/MIPS/kernel/build/linux-2.4.14-mips/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -G 0 -mno-abicalls -fno-pic -mips2 -Wa,-m4100,--trap -pipe -fno-omit-frame-pointer -c -o sched.o sched.c
"-v" will tell me which gas you are using.
H.J.
next prev parent reply other threads:[~2001-11-27 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 5:28 The Linux binutils 2.11.92.0.12 is released H . J . Lu
2001-11-27 15:49 ` Aldy Hernandez
2001-11-27 17:00 ` Johannes Stezenbach
2001-11-27 18:16 ` PATCH: Fix ELF (Re: The Linux binutils 2.11.92.0.12 is released.) H . J . Lu
2001-11-27 18:54 ` Daniel Jacobowitz
2001-11-27 18:25 ` H . J . Lu [this message]
2001-11-27 20:52 ` The Linux binutils 2.11.92.0.12 is released Johannes Stezenbach
2001-11-28 6:55 ` H . J . Lu
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=20011127102550.A30681@lucon.org \
--to=hjl@lucon.org \
--cc=js@convergence.de \
--cc=linux-mips@oss.sgi.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