On Aug 24, 2010, at 2:58 AM, John Barnes wrote:
> Hi,
>
> Over the past 10 years or so, I have been building and using my own
> starlink routines. These have been built using an old version of the
> FIGARO source code. More recently I have built stand-alone routines
> using the starlink cookbook - SC12.
>
> I am now faced with a problem in that recent releases no longer appear
> to include the g95 compiler. However, the program needed for linking
> - alink - still calls g95. I have not been able to get alink and dtask_libtool
> to find the g95 compiler - even when a version is installed in my path.
What is the error message? The problem seems to be that dtask_libtool has the full path of g95 burned into it. Have you tried editing dtask_libtool to include the correct location for the libraries and binary?
> I have tried substituting "gfortran" for "g95" but linking also fails here.
>
The Centos linux releases are built with g95 because the default gfortran on CentOS 5 is too old. The Leopard and Snow Leopard OSX intel releases are built with gfortran. When we finally get to CentOS 6 we'll switch to gfortran for that as well.
I think the link will fail with gfortran because dtask_libtool won't know how gfortran mode is set up and it will fail the link because the runtime symbols will be different.
> Has anyone else got experience building there own routines with recent
> versions of Starlink (I'm running Fedora 13 (64 bit version))?
>
--
Tim Jenness
Joint Astronomy Centre
|