public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16932] Compilation error for sh-coff-gcc little endian target
Date: Sat, 21 Aug 2004 01:53:00 -0000	[thread overview]
Message-ID: <20040821015355.22178.qmail@sourceware.org> (raw)
In-Reply-To: <20040809112414.16932.nitins2@kpitcummins.com>


------- Additional Comments From wilson at specifixinc dot com  2004-08-21 01:53 -------
Subject: Re:  Compilation error for sh-coff-gcc little endian
 target

nitins2 at kpitcummins dot com wrote:
> sh-coff-nm: _ashiftrt.o: File format is ambiguous
> sh-coff-nm: Matching formats: coff-shl coff-shl-small

Maybe it is a binutils problem then.  It could be a problem with coff 
header flags not getting set right for the target.

This might be a good time to learn how binutils works.  Start debugging 
gas/ld/nm to see how they set and use coff header flags.  Start by using 
grep to find where the nm error message is coming from, and then work 
backwards from there to figure out what the problem is.

Another possible solution here is to stop using coff.  coff is obsolete. 
So few people care about it anymore (excluding the MS Windows guys of 
course) that there is really no point to using it, and no point to 
fixing problems with it.  You are probably better off if you remove the 
sh-coff configure support rather than trying to figure out what is wrong 
and fixing it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16932


  parent reply	other threads:[~2004-08-21  1:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 11:24 [Bug c/16932] New: " nitins2 at kpitcummins dot com
2004-08-09 15:45 ` [Bug c/16932] " pinskia at gcc dot gnu dot org
2004-08-09 15:46 ` [Bug target/16932] " pinskia at gcc dot gnu dot org
2004-08-09 16:21 ` pinskia at gcc dot gnu dot org
2004-08-13 12:11 ` nitins2 at kpitcummins dot com
2004-08-14  1:45 ` wilson at specifixinc dot com
2004-08-18 13:02 ` nitins2 at kpitcummins dot com
2004-08-20  3:29 ` wilson at specifixinc dot com
2004-08-20 13:48 ` nitins2 at kpitcummins dot com
2004-08-21  1:53 ` wilson at specifixinc dot com [this message]
2004-12-10  3:17 ` pinskia at gcc dot gnu dot org
2004-12-10  6:06 ` nitins2 at kpitcummins dot com
2004-12-10 13:39 ` pinskia at gcc dot gnu dot org
2004-12-13  9:21 ` nitins2 at kpitcummins dot com

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=20040821015355.22178.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).