On Sat, 18 Dec 2004, Norman Gray wrote:
> Folks,
>
> In the nightly build, dvi2bitmap just failed
> <http://dev.starlink.ac.uk/build/RHEL-WS3-3_X86_64/logs/
> dvi2bitmap.1103338998.log> with
>
> libkpathsea.a(debug.o): relocation R_X86_64_32 can not be used when
> making a shared object; recompile with -fPIC
> /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/
> libkpathsea.a: could not read symbols: Bad value
>
> Does anyone have a very clear idea what that means? It's clearly
> something to do with a 64-bit version of the kpathsea library, but is
> it telling us that (ermmm) /usr/lib64/libkpathsea.a has been built
> incorrectly?
Hi Norman,
no it's saying what the objects in libkpathsea.a are correctly not built
with -fPIC as they are intended for static linking. 64 bit applications
should be linked against the shareable library (which will have been
compiled using -fPIC).
This is the problem I'm fighting, cannot imagine why you're trying to
create a shareable library from the code in libkpathsea.a, however.
Cheers,
Peter.
|