On 26.07.2011 10:44, MacArthur, Ian (SELEX GALILEO, UK) wrote:

>> === making src ===
>> g++ -L. -L/usr/lib64 -Wl,-soname,libfltk.so.1.3 -lXext -lXft
>> -lfontconfig -lXinerama -lpthread -ldl -lm -lX11 -shared
>> -fPIC -o libfltk.so.1.3 ...
>> /usr/bin/ld: Fl.o: relocation R_X86_64_32 against `a local
>> symbol' can not be used when making a shared object;
>> recompile with -fPIC
>> Fl.o: could not read symbols: Bad value
>> collect2: ld returned 1 exit status
>>
>> Does anyone have ideas?

I have no idea. This error message is _very_ cryptic (for me).
What is "R_X86_64_32", and what does "`a local symbol'" mean?
Which "local symbol"?

> I'm not sure if this is a fltk problem or a compiler problem - I
> *suspect* that it is a problem with fltk's configure script, maybe, but
> am not sure. It might be a tools/compiler problem on Centos, though that
> is less likely.
> I do not currently have any x86_64 linux system to test on.

Worked for me on Ubuntu 10.04 LTS (64-bit), configured with
--enable-shared. The shared libs built w/o errors.

> However, lots of libs are suffering from this moving to x86_64, so it's
> all over google...
>
> The gentoo folk have a nice description of things to try here:
>
> http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3
>
> In the short term, try hand-editing the generated makeinclude file and
> add -fPIC to the CFLAGS and CXXFLAGS settings and see if that helps.

Hmm, isn't -fPIC already in the OP'S command line?  At least we can see
it in the linker command, which is probably not where it is needed (?),
but I can see it in my compiler command lines as well.  So I think that
this *should* be okay.

> Please let us know how that goes.
>
> Thanks...

Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to