public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ron McCall <rmccall@sikorsky.com>
To: GCC Help Mailing List <gcc-help@gcc.gnu.org>
Subject: Re: Problem building Solaris hosted PowerPC EABI cross compiler
Date: Sat, 03 Aug 2002 12:28:00 -0000	[thread overview]
Message-ID: <20020803152759.A10586@sikorsky.com> (raw)
In-Reply-To: <20020801172743.A5998@sikorsky.com>; from rmccall@sikorsky.com on Thu, Aug 01, 2002 at 05:27:43PM -0400

Following the instructions at the below URL, I was finally able to build
and install a Solaris hosted PowerPC EABI targeted cross compiler tool
chain (thanks Mumit!).  This includes binutils 2.12.1, gcc 3.1.1 and
newlib 1.10.0.  It is interesting that these instructions seem to merely
avoid running the particular test that was failing before when I
followed Bill Gatliff's CrossGCC FAQ instructions.  The resulting cross
compiler still cannot build an executable by default.

After having done more research into those undefined symbols, I found
that the cross compiler does not by default link in any of the startup
files nor the C library.  I found that adding a compiler option such as
-mads causes it to link in a particular set of startup files (and the C
library) which resolves all those undefined symbols and that the result
of the -mads option is controlled by the specs file.  Now I can work on
adding support for our board!

http://www.nanotech.wisc.edu/~khan/software/gnu-win32/cygwin-to-newlib-cross-howto.txt

Ron McCall

      reply	other threads:[~2002-08-03 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01 14:27 Ron McCall
2002-08-03 12:28 ` Ron McCall [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=20020803152759.A10586@sikorsky.com \
    --to=rmccall@sikorsky.com \
    --cc=gcc-help@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).