Re: f2c obsolete?

[John W. Eaton]

On 24-Oct-2007, Thomas Treichl wrote:

| I'm late (as always) in replying to this thread. A first setup of the fort77 
| program did work for me (with modifications - see below) and it also worked 
to 
| rebuild a new version of Octave.app (that is compiled like Michael's MSVC 
| version with f2c). What I needed to do is to comment out the "BLAS library 
| calling convention compatibility" test result in the configure.in script 
because 
| the test fails for me. See yourself what happens (the -framework vecLib is 
found 
| and needed, this is okay - but the '-framework vecLib' seems to not be passed 
| through correctly through the configure test).
| 
| I changed the script the following way to get some more output:
| 
| line 886:
|    if $have_fortran_compiler; then
|      LIBS="$BLAS_LIBS $FLIBS $LIBS"
|      AC_LANG_PUSH(Fortran 77)
|    echo "--->"
|    echo "-1-> $ac_compile"
|    echo "-2-> $F77"
|    echo "-3-> $FFLAGS"
|    echo "-4-> $ac_ext"
|    echo "--->"
|    echo "-5-> $ac_link"
|    echo "-6-> $ac_exeext"
|    echo "-7-> $FFLAGS"
|    echo "-8-> $LDFLAGS"
|    echo "-9-> $ac_ext"
|    echo "-0-> $LIBS"
|      eval "$ac_compile"
|      eval "$ac_link"
|      AC_LANG_POP(Fortran 77)
|    elif $have_f2c; then
| 
| And the output then is:
| 
|    --->
|    -1-> $F77 -c $FFLAGS conftest.$ac_ext >&5
|    -2-> fort77
|    -3-> -O3 -ftree-vectorize
|      -I/Applications/Octave.app/Contents/Resources/include -mieee-fp -mieee-fp
|    -4-> f
|    --->
|    -5-> $F77 -o conftest$ac_exeext $FFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5
|    -6->
|    -7-> -O3 -ftree-vectorize
|      -I/Applications/Octave.app/Contents/Resources/include -mieee-fp -mieee-fp
|    -8-> -L/Applications/Octave.app/Contents/Resources/lib
|      -L/Applications/Octave.app/Contents/Resources/lib/pkgconfig
|    -9-> f
|    -0->  -framework vecLib -L/Applications/Octave.app/Contents/Resources/lib
|      -lf2c -lhdf5 -lz -lm
|       MAIN foo:
|       MAIN foo:
|    /usr/bin/ld: can't locate framework for: -framework -c
|    collect2: ld returned 1 exit status
|    /Applications/Octave.app/Contents/Resources/bin/fort77: aborting 
compilation
|    ./configure: line 1: ./conftest: No such file or directory
|    no
|    configure: WARNING: Your BLAS library was apparently compiled with a 
Fortran
|    configure: WARNING: compiler that uses a different calling convention from
|    configure: WARNING: the one used by the selected compiler, fort77.
| 
| Any ideas what I can do now?
| 
|    Thomas

Does the following patch help?  Is the "-framework vecLib" option
supposed to be handled by the compiler or linker?  If it is the
compiler instead, then try "-Wc," instead of "-Wl,".

jwe


ChangeLog:

2007-10-24  John W. Eaton  <address@hidden>

        * acx_blas.m4: Use "-Wl,-framework -Wl,vecLib" instead of
        just "-framework vecLib" in test for Mac OS X test.


Index: acx_blas.m4
===================================================================
RCS file: /cvs/octave/acx_blas.m4,v
retrieving revision 1.4
diff -u -u -r1.4 acx_blas.m4
--- acx_blas.m4 6 Dec 2006 20:23:18 -0000       1.4
+++ acx_blas.m4 24 Oct 2007 19:48:15 -0000
@@ -90,7 +90,7 @@
 
 # BLAS in Apple vecLib framework? (Mac OS X)
 if test $acx_blas_ok = no; then
-       vlib_flags="-framework vecLib"
+       vlib_flags="-Wl,-framework -Wl,vecLib"
        save_LIBS="$LIBS"; LIBS="$vlib_flags $LIBS"
        AC_MSG_CHECKING([for $sgemm in $vlib_flags])
        AC_LINK_IFELSE([AC_LANG_CALL([], [$sgemm])],