From: "Dave Williss" <dwilliss@microimages.com>
To: <gcc-help@gcc.gnu.org>
Subject: Can't build gcc 3.1 on AIX
Date: Thu, 12 Sep 2002 10:53:00 -0000 [thread overview]
Message-ID: <131f01c25a85$518201a0$2200000a@opus800> (raw)
I'm having trouble building gcc 3.1 on an AIX (powerpc-aib-aix4.1.4.0)
machine. It gets as far as linking and then gets the following error:
ld: 0711-701 ERROR: TOC overflow. TOC size: 77248 Maximum size: 65536
Any clues how to make it build? I know I've gotten by this in the
past with our own code by passing -mno-fp-in-toc, but I doubt if gcc
is using a lot of FP that would get put into the TOC, so I doubt
if that would help in this case.
I am successfully using 3.1 on an SGI IRIX and on Linux. It also built
fine on Solaris 2.6 and the install just finished.
-- Dave Williss
------
Meddle not in the affairs of dragons,
for you are crunchy and taste good with catsup
next reply other threads:[~2002-09-12 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 10:53 Dave Williss [this message]
2002-09-14 9:39 David Edelsohn
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='131f01c25a85$518201a0$2200000a@opus800' \
--to=dwilliss@microimages.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).