Re: [Toon-members] blas, lapack needing gfortran and MAIN__

[Edward Rosten]

On Wed, 7 Jun 2006, Gerhard Reitmayr wrote:

> I am seeing the same thing here on a SuSe 10.0 box. I think the
> following solves the MAIN__ symbol problem:
>
> mercator gr281: rpm -ql gcc-fortran
> /usr/bin/gfortran
> /usr/lib/gcc/i586-suse-linux/4.0.2/f951
> /usr/lib/libgfortran.a
> /usr/lib/libgfortran.la
> /usr/lib/libgfortran.so
> /usr/lib/libgfortran.so.0
> /usr/lib/libgfortran.so.0.0.0
> /usr/lib/libgfortranbegin.a
> /usr/lib/libgfortranbegin.la
> /usr/share/info/gfortran.info.gz
> /usr/share/man/man1/gfortran.1.gz
>
> mercator gr281: nm /usr/lib/libgfortranbegin.a
>
> fmain.o:
>         U _gfortran_set_args
> 00000000 T main
>         U MAIN__
>
> so we should test for libgfortranbegin.a as well and link against that
> too, that should provide us with the missing MAIN__ symbol??

You should test for the .so if possible. If one _requires_ the other, then 
it should work (ha ha). Run ldd <some_lib.so> to see what the links are. 
It sounds like they are broken in this case.

You may want to look at the configure script for TIFF in libcvd. It's a 
working example of a configure chunk that works properly on "correct" 
machines, as well as some particular instances of b0rked libraries.

You need to be careful since my machine (Redhate Enterprise 4) doesn't 
have (nor does it seem to require) libgfortran.

-Ed