public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mohammed Tajuddin <taj.subhani@oracle.com>
To: amodra@bigpond.net.au, linuxppc64-dev@lists.linuxppc.org,
	gcc@gcc.gnu.org
Subject: TOC overflow on linuxppc64
Date: Fri, 29 Aug 2003 09:02:00 -0000	[thread overview]
Message-ID: <3F4E8DDB.C6EAABE5@oracle.com> (raw)

Hello,

Can someone guide me to fix the problem with TOC overflow on linux
ppc64. After my various attempts building binutils/gcc/glibc following
instructions on linuxppc64.org, I continue to get the same error. 

gnu/local/lib/gcc-lib/powerpc64-linux/3.2.3/crtend.o(.text+0xa): In
function `.__do_global_ctors_aux':
: relocation truncated to fit: R_PPC64_TOC16_DS .toc

I don't have any problems building binutils etc. Somehow I am unable to
get the correct patch although its their on the internet. Following are 
the different versions I have tried so far. 
a. binutils 2.14, gcc 3.2 and glibc 2.3 with the patch
gcc-20030611-ppc64.diff
b. binutils 2.14, gcc 3.1 and glibc 2.3 with the above patch
c. binutils 2.14, gcc 3.3 and glibc 2.3 with the above patch
d. binutils 2.14, gcc 3.2 and glibc 2.2.5 with the above patch
e. binutils 2.14, gcc 3.2 and glibc 2.3 with all the gcc patches on
linuxppc64.org although there were failures while applying the patch.

Appreciate your feedback with the problem of multiple TOC. Please let me
know if anyone has tried, the exact versions of the different tools to
fix this problem. 

Regards,
TAJ

             reply	other threads:[~2003-08-29  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29  9:02 Mohammed Tajuddin [this message]
2003-08-29 13:24 ` Alan Modra
2003-09-02 17:25   ` Mohammed Tajuddin
2003-08-29 17:36 Steve Munroe
2003-08-29 17:42 ` Christoph Hellwig
2003-08-29 17:46   ` Jakub Jelinek

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=3F4E8DDB.C6EAABE5@oracle.com \
    --to=taj.subhani@oracle.com \
    --cc=amodra@bigpond.net.au \
    --cc=gcc@gcc.gnu.org \
    --cc=linuxppc64-dev@lists.linuxppc.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).