From: Joel Sherrill <joel@OARcorp.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: binutils 2.9 powerpc-rtems breakage
Date: Tue, 14 Apr 1998 11:21:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980414123526.1247J-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199804132223.SAA11602@subrogation.cygnus.com>
On Mon, 13 Apr 1998, Ian Lance Taylor wrote:
> Date: Mon, 13 Apr 1998 16:21:53 -0500 (CDT)
> From: Joel Sherrill <joel@OARcorp.com>
>
> I can produce a .s file using -s and then assemble that file with:
>
> ./as -mppc -V -Qy -mrelocatable-lib libgcc2.s
>
> which indicates to me that somehow the rtems configuration lost support
> for the -mlittle option. powerpc-rtems should be identical to
> powerpc-eabi if that trips anyone's memory.
>
> What happens if invoke as directly with -mlittle?
>
> -mlittle still seems to work for me for the powerpc-eabi target. I
> don't know what's happening with your build.
I have not attempted to build powerpc-eabi but I may need to do that.
Something is also failing with mips64orion-rtems that I need to look into.
Anyway, I put the gcc command line in a script and then monkeyed with the
arguments. It looks like -mlittle is enough by itself to break it. It
breaks with all the arguments, just -mlittle, but works will the args
minus -mlittle. See this output from my test script:
+ /usr1/rtems/work/tools/build-powerpc-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-powerpc-tools/gcc/ -O2 -DCROSS_COMPILE
-DIN_GCC -O2 -I./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-fexceptions -Dinhibit_libc -mlittle -mrelocatable-lib -mno-eabi
-mstrict-align -I. -I../../src/gcc -I../../src/gcc/config -DL_muldi3
../../src/gcc/libgcc2.c -c
Assembler messages:
FATAL: Can't create libgcc2.o: Invalid bfd target
+ /usr1/rtems/work/tools/build-powerpc-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-powerpc-tools/gcc/ -O2 -DCROSS_COMPILE
-DIN_GCC -O2 -I./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-fexceptions -Dinhibit_libc -mlittle -mstrict-align -I. -I../../src/gcc
-I../../src/gcc/config -DL_muldi3 ../../src/gcc/libgcc2.c -c
Assembler messages:
FATAL: Can't create libgcc2.o: Invalid bfd target
+ /usr1/rtems/work/tools/build-powerpc-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-powerpc-tools/gcc/ -O2 -DCROSS_COMPILE
-DIN_GCC -O2 -I./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-fexceptions -Dinhibit_libc -mrelocatable-lib -mno-eabi -mstrict-align -I.
-I../../src/gcc -I../../src/gcc/config -DL_muldi3 ../../src/gcc/libgcc2.c
-c
The only things which vary are the arguments:
In (1), -mlittle -mrelocatable-lib -mno-eabi
In (2), -mlittle
In (3), -mrelocatable-lib -mno-eabi
(1) and (2) report the error.
Any ideas on what to look at?
--joel
next parent reply other threads:[~1998-04-14 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199804132223.SAA11602@subrogation.cygnus.com>
1998-04-14 11:21 ` Joel Sherrill [this message]
1998-04-14 10:42 ` Ian Lance Taylor
1998-04-14 11:21 ` Joel Sherrill
1998-04-14 11:21 ` Ian Lance Taylor
1998-04-14 11:58 ` Joel Sherrill
1998-04-14 11:58 ` Ian Lance Taylor
1998-04-14 12:49 ` Joel Sherrill
1998-04-13 14:21 Joel Sherrill
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.980414123526.1247J-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
--cc=ian@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).