OK, digging around in old emails from the end of November last year I see
that the problem is that libf95 needs to be compiled with -fPIC.
Step by tedious step...
Ed
> > /home/echapin/g95-install/bin/../lib/gcc-lib/x86_64-unknown-linux-gnu/4.0.1//libf95.a(transfer.o):
> > relocation R_X86_64_32S against `a local symbol' can not be used when
> > making a shared object; recompile with -fPIC
> > /home/echapin/g95-install/bin/../lib/gcc-lib/x86_64-unknown-linux-gnu/4.0.1//libf95.a:
> > could not read symbols: Bad value
> > make[2]: *** [libchr.la] Error 1
> > make[1]: *** [all] Error 2
> > make: *** [/stardev/manifests/chr] Error 1
> >
> > Does this ring a bell? I seem to remember that I need to set some CFLAGS
> > or something like that.
>
> It looks like you have some 32bit code in there, in which case you'd need
> to set CFLAGS and FCFLAGS to "-m64" to get all the compilers just
> producing 64bit object file, but I'm not 100% sure that's the problem
> here. It could be that you need a sharable library version of libf95 (and
> the error actually means that it cannot create a sharable library because
> transfer.o wasn't compiled with -fPIC). Does that sound more like it?
>
> Cheers,
>
> Peter.
>
|