public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: jacky <jacky@t2-design.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] relocaation truncated ?
Date: Tue, 09 Jan 2001 10:24:00 -0000	[thread overview]
Message-ID: <3A5B5748.9DD71076@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101091717320.27741-100000@t2os.zh.t2-design.com>

jacky wrote:
> 
> Hi all;
> 
>     I am porting viewml to ecos,but I meet a problem, can someone do me a
> favor to tell me how to solve this. THe following is the error messages:
> 
>  html.o:/home/root/myprojects/mips_for/viewml-0.15/src/g++/stl_alloc.h
>           :473: relocation truncated to fit: R_MIPS_GPREL16
>           __default_alloc_template<false, 0>::start_free
> 
> What is the meaning of R_MIPS_GPREEL16, what will cause this kind of
> error?  Thank you!

Sometimes you see this simply when the symbol isn't found, and another line
of the error message should also help indicate this.

Otherwise it can mean that a 16-bit GP relative relocation was not large
enough to contain the relocation actually needed. This type of thing
happens when two modules access the same symbol, but do so in a different
way, e.g.

int myarray[1];

in one module, which actually is:

int myarray[10];

in a different module. Anything using the first prototype would be given a
smaller relocation than in the latter case.

In other words, it can happen when two modules have two different types for
the same "thing".

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

      reply	other threads:[~2001-01-09 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  1:26 jacky
2001-01-09 10:24 ` Jonathan Larmour [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=3A5B5748.9DD71076@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jacky@t2-design.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).