> It *looks* like libf95.a needs to be rebuilt with -fPIC. I misread this
> earlier but it's not a chr error it's a libf95.a error. In principle you
> can download the g95 source and remake just the libf95.a with -fPIC (it's
> not a big job - it's a tar ball within the g95 tarball so you don't need
> to build g95 from source to rebuild the run time library).
>
> Are you using a full 64bit OS or a mixed system?
When I installed FC4 I also installed the 32bit compatibility libraries
(so I have a /usr/lib and /usr/lib64), but the kernel etc. are 64bit. Is
there a possibility that starlink is getting confused by the presence of
some 32bit libraries?
I think that this must be a compiler problem. However, I was using a
nightly build of starlink to do SMURF development (which was linking
against starlink fortran libraries) and didn't seem to have any problem.
I'll try your suggestion tomorrow.
Cheers,
Ed
|