From: Stephane GEORGES <sg@dalim.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: R_PPC_REL24 relocation out of range
Date: Tue, 23 Nov 1999 14:03:22 +0100 [thread overview]
Message-ID: <383A909A.16FCF296@dalim.de> (raw)
I am porting some code from linux Intel to linuxppc.
My executables have a plugin notion that allow people to add
some new functionalities to program (like photoshop plugins).
My plugins are shared libraries whose name does not start
with lib (like jobs.so.1.0).
These plugins can link on common shared libraries because
they implement the same main classes.
My issue is that I get such an error message when the second
plugin is beeing loaded (via dlopen)
jobs.so.1.0: R_PPC_REL24 relocation out of range (for instance)
If I rename my plugins adding lib in front of the name, then,
it works correctly (libjobs.so.1.0).
Could someone help me so that it works without the lib added
in front of the shared library name ?
Does ld have special options so that it works ?
(I have glibc-2.1.1-6c and my kernel is a 2.2.13).
The same code works correctly on my linux Intel (with same
version of glibc).
--
/====================================================================/|
| Stephane GEORGES | ||
| DALiM SOFTWARE GmbH R&D | Tel: +49 7851 9196 40 ||
| Strassburger Str.6 | Fax: +49 7851 7357 6 ||
| D-77696 | ||
| Kehl-Sundheim (Germany) | E-mail: sg@dalim.de ||
|____________________________________________________________________|/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-23 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 13:03 Stephane GEORGES [this message]
1999-11-23 13:35 ` R_PPC_REL24 relocation out of range Andreas Tobler
1999-11-23 14:47 ` Michael Schmitz
[not found] <A5D247E9DC04C08EC1256832004AFECD.004AFF0FC1256832@kehl.dalim.de>
1999-11-23 16:31 ` Stephane GEORGES
1999-11-23 16:45 ` Andreas Tobler
-- strict thread matches above, loose matches on Subject: below --
2001-07-20 13:30 David Burg
2001-07-20 15:56 ` David Burg
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=383A909A.16FCF296@dalim.de \
--to=sg@dalim.de \
--cc=linuxppc-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 NNTP newsgroup(s).