From: Ricardo Anguiano <anguiano@codesourcery.com>
To: "J. Scott Edwards" <sedwards@xmission.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC 3.2 on Playstation 2 mips
Date: Wed, 30 Oct 2002 21:00:00 -0000 [thread overview]
Message-ID: <m3y98fgq3t.fsf@mordack.codesourcery.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0210301944190.24916-100000@xmission.xmission.com>
"J. Scott Edwards" <sedwards@xmission.com> writes:
> On 30 Oct 2002, Ricardo Anguiano wrote:
> > "J. Scott Edwards" <sedwards@xmission.com> writes:
> > > I'm trying to upgrade the compiler on Linux Playstation 2 from
> > > 2.95.2 to 3.2. I've tried the ./configure; make bootstrap with some
[...]
> >
> > >From your statements above, it looks like your build directory is the
> > same as your source directory, which is not supported.
[...]
>
> No, I'm building in a separate directory. I'm trying to follow the
> installation instructions as closely as possible. This is the end of the
> make:
>
[...]
> ./xgcc -B./ -B/usr/local/mipsel-pc-linux-gnu/bin/ -isystem /usr/local/mipsel-pc-linux-gnu/include -isystem /usr/local/mipsel-pc-linux-gnu/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc-3.2/gcc -I../../gcc-3.2/gcc/. -I../../gcc-3.2/gcc/config -I../../gcc-3.2/gcc/../include -DL_divdi3 -c ../../gcc-3.2/gcc/libgcc2.c -fexceptions -fnon-call-exceptions -o libgcc/./_divdi3.o
> /tmp/cc0GVsc4.s: Assembler messages:
> /tmp/cc0GVsc4.s:1175: Error: Can not represent BFD_RELOC_32_PCREL relocation in this object file format
> /tmp/cc0GVsc4.s:1205: Error: Can not represent BFD_RELOC_32_PCREL relocation in this object file format
> make[3]: *** [libgcc/./_divdi3.o] Error 1
> make[3]: Leaving directory `/usr.orig/src/gcc3/gcc'
> make[2]: *** [libgcc.a] Error 2
> make[2]: Leaving directory `/usr.orig/src/gcc3/gcc'
> make[1]: *** [stage1_build] Error 2
> make[1]: Leaving directory `/usr.orig/src/gcc3/gcc'
> make: *** [bootstrap] Error 2
This is good, but over my head. I suggest reposting this information
on the main gcc list (gcc@gnu.org) with your configure line, the
source you are using (looks like 3.2 release), and the compiler you
are using to build, along with the platform information (uname -a or
similar), and importantly the error message above.
I don't know the answer, but if I had to guess, I would say this is a
problem with an out of date assembler (.s -> .o) and thus a stale
binutils. The assembler doesn't know how to handle the
BFD_RELOC_32_PCREL relocation in a.out/elf or whatever object format
you are using. If you don't get any responses, try a newer version of
binutils. The newer assembler might know how to handle that
relocation.
HTH,
--
Ricardo Anguiano
CodeSourcery, LLC
prev parent reply other threads:[~2002-10-31 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 10:00 J. Scott Edwards
2002-10-30 16:29 ` Ricardo Anguiano
2002-10-30 20:17 ` J. Scott Edwards
2002-10-30 20:54 ` gcc-help@gcc.gnu.org vetcha prasad kumar
2002-10-30 21:00 ` Ricardo Anguiano [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=m3y98fgq3t.fsf@mordack.codesourcery.com \
--to=anguiano@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sedwards@xmission.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).