Re: can gnustep libraries be pic-enabled?

[Richard Frith-Macdonald]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 6 Nov 2006, at 05:59, tgate wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Is there a way to pic-enable the libraries when building the  
> gnustep tools?

That's done by default ... you can build using 'messages=yes' to see  
the exact commands used and confirm that -fPIC is used, and if it  
isn't (unlikeley) you presumably have a problem in the make package.

> To try and test seg fault problems I'm having on a core 2 duo I  
> created
> the same setup on another machine which is AMD64 and tried to  
> compile on
> that machine but I get this error:
>
>  Linking library libgnustep-base ...
> /usr/lib64/gcc/x86_64-suse-linux/4.1.0/../../../../x86_64-suse- 
> linux/bin/ld:
> /usr/local/lib/libcallback.a(misc.o): relocation R_X86_64_32  
> against `a
> local symbol' can not be used when making a shared object; recompile
> with -fPIC
> /usr/local/lib/libcallback.a: could not read symbols: Bad value

Looks like a problem in libcallback rather than in GNUstep.

You can try getting the source of ffcall and building that as 64bit  
PIC rather than using the version which came with your system ...  
probably you need to do something like CC='gcc -fPIC' when  
configuring ffcall.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFTt9GSZ/wVHjv7MIRAlCSAKCtt0RytAUJll7fNXcNjhODtlbiFgCeMLIe
X5PLH/UwWMRmVX7yoXtor5E=
=47ou
-----END PGP SIGNATURE-----