linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Pierre Sarrazin <sarrazip@machinasapiens.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: R_PPC_REL24 relocation out of range, with trivial program
Date: Mon, 3 Apr 2000 23:34:02 +0200	[thread overview]
Message-ID: <00040323364000.01288@enzo.bigblue.local> (raw)
In-Reply-To: <38E90159.DB89C967@machinasapiens.com>


Am Mon, 03 Apr 2000 schrieb Pierre Sarrazin:
>Last month I posted the following message:
>
>From: Pierre Sarrazin
>Date: Thu, 02 Mar 2000 18:25:46 -0500
>> This is another message about the "R_PPC_REL24 relocation out of range"
>> problem. I have a trivial program and library system that illustrates it.
>> I have read some of the previous messages on this topic but the solutions
>> proposed did not make a difference.
>>
>> The problem happens when the dlopened library exports a C++
>> function returning 'string', but not when it exports a function
>> returning 'const char *'.
>>
>> Here is the program:
>	[...]
>
>
>The full message is at:
>http://lists.linuxppc.org/listarcs/linuxppc-dev/200003/msg00025.html
>
>
>I would like to know if there is a chance that this problem will
>be fixed soon. I have had to suspend my LinuxPPC work for the
>last month. My company's support for the LinuxPPC platform is
>delayed by this issue.
>
>Is there a way to ask gcc to generate only long branch instructions
>so as to avoid this whole problem? Thanks.

This seems to be fixed in the current toolchain:

[fsirl@entropy:~/bugs/reloc]$ make
g++ -g -Wall -fPIC -DSTRING_EXAMPLE -c prog.cpp
g++ -g -Wall -fPIC -DSTRING_EXAMPLE -o prog prog.o -ldl
g++ -g -Wall -fPIC -DSTRING_EXAMPLE -c f.cpp
g++ -shared -o libf.so f.o
[fsirl@entropy:~/bugs/reloc]$ ./prog
f()
s = [pizza]

Either upgrade your distribution or go to
<ftp://devel.linuxppc.org/users/fsirl>.

Franz.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-04-03 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03 20:38 R_PPC_REL24 relocation out of range, with trivial program Pierre Sarrazin
2000-04-03 20:46 ` David Edelsohn
2000-04-03 21:34 ` Franz Sirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-02 23:25 Pierre Sarrazin

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=00040323364000.01288@enzo.bigblue.local \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sarrazip@machinasapiens.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 NNTP newsgroup(s).