Re: help needed: fortran library linking issue.

On Mon, Sep 27, 2010 at 14:33 -0500, Freddy Martinez wrote:
> Thanks for the help John.
> 
> I believe the compilers are the same. I have not gotten the errors
> that would arise if the compilers are mismatched.
> 
> I am building with gcc 4.4.5 and gfortran 4.4.
> 
> I have attached the logs
> 
> Best,
> 
> FM
[...]
>   $ ./configure --with-headas=/home/freddy/Projects/Research/heasoft-6.9/x86_64-unknown-linux-gnu-libc2.5 --with-xspec-version=12

Did you compile heasoft yourself using gcc-4.4.5 and
gfortran-4.4, or did you install pre-compiled binaries?

I ask in part because the heasoft path above refers to libc2.5
which seems relatively old compared to all the other software
you're using (gcc-4.4, linux kernel 2.6.35-22 etc.) If you had
compiled heasoft yourself, I would have expected a newer libc
version. For example, on my debian-based system, I have gcc-4.3
and libc2.7.

I think this is relevant because the _gfortran_copy_string
problem you reported was commonly encountered with old compiler
versions, e.g. gfortran-4.1

If heasoft was pre-compiled using an older gfortran, then that
might be the problem.  This seems consistent with the heasoft
release notes regarding portability of pre-compiled linux binaries:

  http://heasarc.gsfc.nasa.gov/docs/software/lheasoft/linux.html

If that's the problem, then compiling heasoft from source using
gcc-4.4, gfortran-4.4, etc. should fix it.

I think heasoft also suggests a workaround (see the above URL),
but I haven't tried that approach.

Does that help?

Thanks,
-John
----
You received this message because you are
subscribed to the isis-users list.
To unsubscribe, send a message to
isis-users-request_at_email.domain.hiddenwith the first line of the message as:
unsubscribe