From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: binutils 2.9 mips64orion-rtems breakage
Date: Tue, 14 Apr 1998 11:21:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980414124206.1247K-100000@vespucci.advicom.net> (raw)
This target is broken also in binutils 2.9. It worked in gas-980314. The
build proceeds fine through the -msingle-float version of libgcc2 but
ar begins reporting "Invalid operation" as it gets to the -EL version.
do \
echo ${name}; \
/usr1/rtems/work/tools/build-mips64orion-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-mips64orion-tools/gcc/ -O2 -DCROSS_COMPILE
-DIN_GCC -O2 -I./include -G 0 -g1 -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -fexceptions -Dinhibit_libc -EL -I.
-I../../src/gcc -I../../src/gcc/config -c -DL${name} \
../../src/gcc/libgcc2.c -o ${name}.o; \
if [ $? -eq 0 ] ; then true; else exit 1; fi; \
/usr1/rtems/work/tools/build-mips64orion-tools/binutils/ar rc
tmplibgcc2.a ${name}.o; \
rm -f ${name}.o; \
done
_muldi3
_divdi3
/usr1/rtems/work/tools/build-mips64orion-tools/binutils/ar: tmplibgcc2.a:
Invalid operation
_moddi3
------------------------------
Later it finally dies as it does the following:
LIBGCC2_CFLAGS="-O2 -DCROSS_COMPILE -DIN_GCC -O2 -I./include -G 0
-g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fexceptions -Dinhibit_libc
-EL" ; \
fi
rm -rf tmplibgcc.a tmpcopy
mkdir tmpcopy
if [ x != x ]; \
then (cd tmpcopy;
/usr1/rtems/work/tools/build-mips64orion-tools/binutils/ar x ../); \
else true; \
fi
(cd tmpcopy; /usr1/rtems/work/tools/build-mips64orion-tools/binutils/ar x
../libgcc2.a)
/usr1/rtems/work/tools/build-mips64orion-tools/binutils/ar: ../libgcc2.a:
Invalid operation
Any ideas?
--joel
reply other threads:[~1998-04-14 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.BSF.3.96.980414124206.1247K-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).