help-octave
[Top][All Lists]
Advanced

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

Re: problem (and workaround) compiling arpack-ng_3.1.0


From: Sergei Steshenko
Subject: Re: problem (and workaround) compiling arpack-ng_3.1.0
Date: Sat, 12 May 2012 10:59:48 -0700 (PDT)




----- Original Message -----
> From: Sergei Steshenko <address@hidden>
> To: "address@hidden" <address@hidden>
> Cc: 
> Sent: Saturday, May 12, 2012 8:14 PM
> Subject: problem (and workaround) compiling arpack-ng_3.1.0
> 
> Hello,
> 
> since arpack-ng_3.1.0 is also developed by Octave developers, this may be a 
> proper list to publish my findings.
> 
> I had my "favorite" "'make' fails even though 
> 'configure' is OK" problem, particularly, the message was:
> 
> "
> 
> make[3]: Entering directory 
> `/mnt/sdb8/sergei/AFSWD_debug/build/arpack-ng_3.1.0/PARPACK/UTIL/MPI'
> /mnt/sdb8/sergei/AFSWD_debug/20120424/bash-4.2/bin/bash ../../../libtool 
> --tag=F77   --mode=compile   -g -O2 -c -o pivout.lo pivout.f
> libtool: compile: unrecognized option `-g'
> ".
> 
> Actually, there are two problematic files producing such error messages:
> 
> arpack-ng_3.1.0/PARPACK/UTIL/MPI/Makefile
> arpack-ng_3.1.0/PARPACK/SRC/MPI/Makefile
> 
> - somehow F77 is undefined in them - I am using self-built gcc-4.5.3 and it 
> has 
> 'gfortran' and in other places, starting from 'configure', it 
> works OK.
> 
> The workaround is to run 'make F77=gfortran' rather than just 
> 'make'.
> 
> I think this should be fixed.
> 
> Thanks,
>   Sergei.
> 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave

Oh, the issue has already been reported: 
http://forge.scilab.org/index.php/p/arpack-ng/issues/689/ , and they offer a 
different workaround.

Whatever.

Regards,
  Sergei.




>


reply via email to

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