octave-maintainers
[Top][All Lists]
Advanced

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

Re: 3.2.0 release candidate 5: problems with blas/lapack


From: Jean-Francois Cardoso
Subject: Re: 3.2.0 release candidate 5: problems with blas/lapack
Date: Wed, 3 Jun 2009 15:20:41 -0700 (PDT)



Rob Mahurin wrote:
> 
> On Jun 2, 2009, at 4:30 PM, Jean-Francois Cardoso wrote:
>> Hello Jaroslav,
>>
>> I have problem building all 3.2.0 release candidates.
>> The configure script does not detect properly the
>> BLAS libraries.  This is happening on two machines of mine:
>>
>> 1) on my MacBook where ./configure spills out:
>>
>> [...]
>> checking whether DDOT is called correctly from Fortran... yes
>> checking whether CDOTU is called correctly from Fortran... no
>> checking whether ZDOTU is called correctly from Fortran... yes
>> configure: WARNING: A BLAS library was detected but found  
>> incompatible with
>> your Fortran 77 compiler.
>> [...]
> 
> I had this problem while using the compiler "g95" that shipped with  
> OSX 10.5.7.  I got around it by installing gcc44 from macports and  
> calling configure with
> 
>       ./configure LDFLAGS=-L/opt/local/lib LIBS=-lmetis \
>       FFLAGS=-ff2c F77=gfortran-mp-4.4 \
>       CC=gcc-mp-4.4 CXX=g++-mp-4.4
> 
>>
> 
> You seem to be doing something more complicated than I am with BLAS  
> libraries, but hopefully this helps anyway.
> 
> 


Thanks for your reply.  Indeed, the BLAS detection problem is solved
by adding the ff2c switch.   This works on both MacOSX
and on a Linux+MKL system.  No test failures on Linux+MKL
but several on MacOSX, which I will report separately.
I am wondering if the ff2c switch induces some loss 
of efficiency.  If not, why is it not "on" by default; if yes,
any idea about the possible loss ?  (this is out of curiosity).

Thanks again, JF







-- 
View this message in context: 
http://www.nabble.com/3.2.0-release-candidate-5-tp23829104p23860608.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.



reply via email to

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