[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: R_PPC_REL24 relocation...out of range
From: |
kisch+opensubscriber |
Subject: |
Re: R_PPC_REL24 relocation...out of range |
Date: |
Mon, 22 Jan 2007 18:50:30 +0800 |
Hi Warren,
I've been running into the same problem like you.
Adam Fedor is right - it's most probably ffcall which has not been built using
-fPIC.
You're right that the configure script of ffcall correctly detects that it
should use -fPIC to have the compiler generate position-independent code.
But then it proceeds by simply not using that option for the build ;-)
The problem is this: The ffcall package is capable of building a static and and
a shared library package. The shared library is built with -fPIC allright. The
static library is built without -fPIC. But now gnustep-base builds its shared
library using the STATIC ffcall lib, which doesn't have -fPIC. Therefore the
linker complaints.
My solution: configure ffcall with CFLAGS set to include -fPIC
(CFLAGS="-whatever-other-options -fPIC" ./configure --enable-static).
Then rebuild ffcall and gnustep-base.
Hope this helps,
- Bernd Kischnick
P.S.
by the way, I'm building RPM packages for gnustep on PowerPC.
I can send them to you if you're interested.
-- Warren Nagourney wrote :
I compiled ffcall from source and noticed that it seemed to have
automatically used the -fPIC option (this from the stuff that appeared
during configure).
Adam Fedor wrote:
>
> It's likely that there is a non-gnustep library that is causing the
> problems. Most likely it is ffcall, if you are using it. Try
> recompiling and installing ffcall with -fPIC to see if that works
> (also recompile gnustep-base).
--
This message was sent on behalf of kisch+opensubscriber@sesamstrasse.dyndns.tv
at openSubscriber.com
http://opensubscriber.com/message/bug-gnustep@gnu.org/5596062.html
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: R_PPC_REL24 relocation...out of range,
kisch+opensubscriber <=