public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com
Cc: gas2@cygnus.com
Subject: Re: binutils 2.9 powerpc-rtems breakage
Date: Tue, 14 Apr 1998 10:42:00 -0000	[thread overview]
Message-ID: <199804141742.NAA16146@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.980414123526.1247J-100000@vespucci.advicom.net>

   Date: Tue, 14 Apr 1998 12:39:55 -0500 (CDT)
   From: Joel Sherrill <joel@OARcorp.com>

   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:

   ...

   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?

Well, first try to recreate it by invoking gas directly, without
getting involved with gcc.

Once you can do that, set a breakpoint on output_file_create in gas,
and see what format it is passing to bfd_openw, and see why that
format is not defined by BFD.

Ian

  reply	other threads:[~1998-04-14 10:42 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
1998-04-14 10:42   ` Ian Lance Taylor [this message]
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=199804141742.NAA16146@subrogation.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=joel@OARcorp.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).