public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Butcher <M_J_BUTCHER@compuserve.com>
To: "INTERNET:huntbs@mailcity.com" <huntbs@mailcity.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Cross compiler won't build
Date: Fri, 07 Jun 2002 12:55:00 -0000	[thread overview]
Message-ID: <200206071555_MC3-1-164-F842@compuserve.com> (raw)

Hi Brett

Another small detail.

I have realised that the problem with the last binutils build was not with
the compiler but with linking a function which could not be found.
print_insn_mcore() is exported in the file mcore-dis.c and seems to be in
the library libopcodes.a which was build somewhere along the line.

Interestingly I have now exactly the same error when repeating the exercise
with the Mcore target again. This means that the original failed build of
the Mcore cross-compiler must screwed something up so that the linker can
not find this library anymore - time to clean up the disk and start again..

I'll get it soon.

Cheers

Mark

             reply	other threads:[~2002-06-07 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 12:55 Mark Butcher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-07 11:56 Mark Butcher
2002-06-07  9:10 Brett Hunt
2002-06-07  7:47 Mark Butcher
2002-06-05 16:06 Mark Butcher

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=200206071555_MC3-1-164-F842@compuserve.com \
    --to=m_j_butcher@compuserve.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=huntbs@mailcity.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).