From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: gcc@gcc.gnu.org
Subject: what binutils for m68hc11-elf and gcc 3.3-branch
Date: Thu, 20 Feb 2003 14:14:00 -0000 [thread overview]
Message-ID: <3E54DEA4.6EB4BD16@OARcorp.com> (raw)
Hi,
In trying to test the 3.3 branch, I have run into what appears to
be a binutils/gcc version mismatch. binutils 2.13.2.1 doesn't
appear to have the directives .long and .long-double as gcc 3.3-branch
assumes. Is this a mistake in gcc or a binutils version mismatch?
If it is a binutils mismatch, then gcc is assuming a non-released
version.
/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-m68hc11-elf/gcc/xgcc
-B/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-m68hc11-elf/gcc/ -nostdinc
-B/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-m68hc11-elf/m68hc11-elf/newlib/
-isystem
/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/b-m68hc11-elf/m68hc11-elf/newlib/targ-include
-isystem
/opt/usr3/ftp_archive/gnu/gcc/ss/b-3.3/gcc-3.3-branch/newlib/libc/include
-B/opt/gnucross-test/m68hc11-elf/bin/
-B/opt/gnucross-test/m68hc11-elf/lib/ -isystem
/opt/gnucross-test/m68hc11-elf/include -Os -mrelax -DUSE_GAS -DIN_GCC
-g -DIN_LIBGCC2 -I. -I. -I../../gcc-3.3-branch/gcc
-I../../gcc-3.3-branch/gcc/. -I../../gcc-3.3-branch/gcc/config
-I../../gcc-3.3-branch/gcc/../include -DL_mulsi3 -xassembler-with-cpp -c
../../gcc-3.3-branch/gcc/config/m68hc11/larith.asm -o libgcc/./_mulsi3.o
Assembler messages:
Error: Option `long' is not recognized.
Error: Option `long-double' is not recognized.
larith.asm:41: Error: unknown pseudo-op: `.mode'
make[2]: *** [libgcc/./_mulsi3.o] Error 1
Advice appreciated.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2003-02-20 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 14:14 Joel Sherrill [this message]
2003-02-20 22:40 ` Stephane Carrez
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=3E54DEA4.6EB4BD16@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gcc@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).