From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
Subject: Re: current cvs binutils and mipsel-linux kernel
Date: Mon, 10 Jul 2000 19:29:18 +0200 [thread overview]
Message-ID: <20000710192918.A5900@bacchus.dhis.org> (raw)
In-Reply-To: <20000710011846.A1275@paradigm.rfc822.org>; from flo@rfc822.org on Mon, Jul 10, 2000 at 01:18:46AM +0200
On Mon, Jul 10, 2000 at 01:18:46AM +0200, Florian Lohoff wrote:
> it seems there is a problem in the binutils from current cvs ...
>
> mipsel-linux-gcc -D__KERNEL__ -I/home/flo/mips/dec/src/linux-2.4.0-test3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips2 -pipe -fno-strict-aliasing -c softfp.S -o softfp.o
> softfp.S: Assembler messages:
> softfp.S:225: Error: illegal operands `la'
> softfp.S:225: Error: unrecognized opcode `cvt'
> softfp.S:225: Error: Rest of line ignored. First ignored character is `.'.
> make[1]: *** [softfp.o] Error 1
> make[1]: Leaving directory `/home/flo/mips/dec/src/linux-2.4.0-test3/arch/mips/kernel'
> make: *** [_dir_arch/mips/kernel] Error 2
You're probably also using a very recent gcc. Recent gcc had preprocessor
changes to make it more stricly comply to ISO. This breaks a number of
files in the Linux kernel which for readability have extra space around
the ## C preprocessor paste. I've already commited the necessary fixes
for softfp.S which is the only affected MIPS file to CVS. There is still
a large number of other files which aren't ISO C89 compliant. Keith
Wesolowski has made a patch for those which I'll send to Linus.
Ralf
prev parent reply other threads:[~2000-07-10 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-09 23:18 current cvs binutils and mipsel-linux kernel Florian Lohoff
2000-07-10 3:45 ` Keith M Wesolowski
2000-07-10 17:29 ` Ralf Baechle [this message]
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=20000710192918.A5900@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-mips@vger.rutgers.edu \
/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.