public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@OARcorp.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: source of powerpc-rtems failure
Date: Thu, 16 Apr 1998 12:23:00 -0000	[thread overview]
Message-ID: <Pine.BSF.3.96.980416140908.26940O-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199804161846.OAA23028@subrogation.cygnus.com>

On Thu, 16 Apr 1998, Ian Lance Taylor wrote:

>    tdefaults =  -DDEFAULT_VECTOR=bfd_elf32_powerpc_vec
> 
> That by itself is not a bug.  If you configure with
> --enable-targets=all, SELECT_VECS is not supposed to be defined.
> SELECT_VECS is only defined if you have a list of selected vectors.

Thanks.  I was trying to track it down but did not understand the magic
going on behind the screen. :)

> The bug would seem to be that bfd_elf32_powerpcle_vec is not in the
> default list of targets in targets.c.

This lets it get further and now it fails in the same way the mips64orion
did.  It builds at least one multilib version of tmplibgcc2.a and then
complains ...:

build-powerpc-tools/gcc/ -O2  -DCROSS_COMPILE -DIN_GCC    -O2 -g
-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 -c -DL${name} \
      ../../src/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  /usr1/rtems/work/tools/build-powerpc-tools/binutils/ar rc tmplibgcc2.a
${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
_divdi3
/usr1/rtems/work/tools/build-powerpc-tools/binutils/ar: tmplibgcc2.a:
Invalid operation

It does this repeatedly until the rule stmp-multilib-sub fails.  Is this a
related problem but in ar?

I will start to see what I can figure out about this one. :)

--joel


      reply	other threads:[~1998-04-16 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-16 10:56 Joel Sherrill
1998-04-16 11:46 ` Ian Lance Taylor
1998-04-16 12:23   ` Joel Sherrill [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=Pine.BSF.3.96.980416140908.26940O-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).