octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Build problem (what.m missing?)


From: John W. Eaton
Subject: Re: CVS Build problem (what.m missing?)
Date: Fri, 26 Oct 2007 14:16:45 -0400

On 26-Oct-2007, Fredrik Lingvall wrote:

| configure:13888: result: yes
| configure:14095: checking BLAS library calling convention compatibility
| configure:14138: result: no
| configure:14140: WARNING: Your BLAS library was apparently compiled with
| a Fortran
| configure:14142: WARNING: compiler that uses a different calling
| convention from
| configure:14144: WARNING: the one used by the selected compiler, gfortran.
| configure:14146: error: You must correct this problem before building
| Octave.
| 
| 
| I had some initial problems compiling the foo.f. It seems that gfortran
| i picky regarding white space.
| Compiling:
| 
| program foo
|       double complex zdotu, zx(10), zy(10), retval
|       integer n, incx, incy
|       n = 10
|       incx = 1
|       incy = 1
|       do 10 i = 1, n
|          zx(i) = dcmplx (i, 0)
|          zy(i) = dcmplx (0, i)
|  10   continue
|       retval = zdotu (n, zx, incx, zy, incy)
|       if (retval .eq. dcmplx (0, 385)) then
|          print *, 'succeeded'
|       else
|          print *, 'failed'
|          print *, retval
|       endif
|       end
| 
| gives the error,
| 
| fllap4 octave # gfortran foo.f -L/usr/local/lib -lBLAS -lLAPACK
|  In file foo.f:1
| 
| program foo
| 1
| Error: Non-numeric character in statement label at (1)
|  In file foo.f:1
| 
| program foo
| 1
| Error: Unclassifiable statement at (1)

That's very strange because the configure script has

cat << EOF > conftest.f
      program foo
      double complex zdotu, zx(10), zy(10), retval
      integer n, incx, incy
      n = 10
      incx = 1
      incy = 1
      do 10 i = 1, n
        zx(i) = dcmplx (i, 0)
        zy(i) = dcmplx (0, i)
   10 continue
      retval = zdotu (n, zx, incx, zy, incy)
      if (retval .eq. dcmplx (0, 385)) then
        print *, 'succeeded'
      else
        print *, 'failed'
        print *, retval
      endif
      end
EOF

so I don't understand where the leading spaces on the "program foo"
line went.  They are definitely present in my configure.in and the
generated configure file.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]