public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: help-gcc@gnu.org
Subject: Re: GCC-2.95.2 and AIX v4.3.3 compile errors w/egcs-2.91.66
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <xytyab0haar.fsf@mal-ach.watson.ibm.com> (raw)
Message-ID: <19991231222400.3Vf6sLi-DRtTEoQYyLimFhwfg7788TUsYhtDmsVPGGc@z> (raw)
In-Reply-To: <3850F50E.C2D65FCE@us.ibm.com>

>>>>> Ed Geraghty writes:

Ed> If this subject seems familar well it should... I had posted a
Ed> message just a few hours ago when I was trying to compile gcc-2.95.2
Ed> with the AIX v4.3.3 native compiler. Running out of time I tried using a
Ed> version of egcs I have allready compiled under AIX v4.3.2. Just
Ed> wondering does anybody have any suggestions how to fix this?

	First, you cannot simply start from where you left off building
with AIX XLC and switching to GCC.  Second, you really need to read the
installation instructions despite your short amount of time.  If you had
read the installation instructions, you would have see that one should
build the compiler with "make bootstrap" which specifically invokes the
linker to solve the TOC overflow problem.

David
-- 
===============================================================================
David Edelsohn                                      T.J. Watson Research Center
dje@watson.ibm.com                                  P.O. Box 218
+1 914 945 4364 (TL 862)                            Yorktown Heights, NY 10598

  parent reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-10  4:43 Ed Geraghty
1999-12-10 10:19 ` Greg Wimpey
1999-12-31 22:24   ` Greg Wimpey
1999-12-11 23:46 ` David Edelsohn [this message]
1999-12-31 22:24   ` David Edelsohn
1999-12-31 22:24 ` Ed Geraghty

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=xytyab0haar.fsf@mal-ach.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=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).