Re: eigs and Octave.app

[Henry F. Mollet]

on 11/12/07 9:28 AM, Thomas Treichl at address@hidden wrote:

> Mark McClure schrieb:
>> ----- Original Message -----
>> From: David Bateman <address@hidden>
>> 
>>> Isn't Octave.app compiled with f2c as Apple in their wisdom choose
>>> not to supply a fortran compiler in their Xcode suite.. That is
>>> probably the issue. Perhaps Arpack can be compiled with f2c as
>>> well..
>> 
>> 
>> I suppose this makes sense; thanks for the info.
>> 
>> Two questions:
>>  1) Has anyone had success with eigs on a Mac?  Perhaps,
>>     via direct compilation of Octave as described here:
>>     http://wiki.octave.org/wiki.pl?OctaveForMac
> 
> Hallo Mark,
> 
> please report if this works for you, the text describes how to install the
> ARPACK software before the Octave-forge arpack package can be installed and
> this text also will be part of the Readme.html file (if it works for you like
> it does work for me) of the next Octave.app release.
> 
>    Thomas
> 
> How can I install the Arpack­package from Octave­Forge that also depends
> further
> libraries?
> ==============================================================================
> ==
> 
> As described previously you need to download, configure, compile and install
> the 
> needed ARPACK-software before you install the Octave­Forge package.
> 
> 1. Download a current version of the ARPACK­software and the patch that is
> available, eg.
> 
>    bash ~$ curl -s -S \
>      http://www.caam.rice.edu/software/ARPACK/SRC/arpack96.tar.Z \
>      -o arpack96.tar.Z
>    bash ~$ curl -s -S \
>      http://www.caam.rice.edu/software/ARPACK/SRC/patch.tar.Z \
>      -o patch.tar.Z
> 
> 2. Unpack the downloaded files, patch the codes and change into the directory
> that has been created, eg.
> 
>    bash:~$ tar -xzf arpack96.tar.Z
>    bash:~$ tar -xzf patch.tar.Z
>    bash:~$ cd ARPACK
>    bash:~/ARPACK$
> 
> 3. Edit the file ARmake.inc and change the values of the following variables
> in 
> a similiar way, eg.
> 
>    # this is the location of your current ARPACK directory that has been
> created
>    home = $(HOME)/ARPACK
> 
>    # this actually only results in the name of the created libarpack_${PLAT}.a
> 
>    PLAT = MAC
> 
>    # remove the option -cg89 that is not compatible with fort77
>    FFLAGS = -O
> 
>    # use backslashes without spaces here and use tabulators at the
>    # beginnings of the lines
>    FC = PATH=/Applications/Octave.app/Contents/Resources/bin:${PATH}\
>            /Applications/Octave.app/Contents/Resources/bin/fort77\
>            -I/Applications/Octave.app/Contents/Resources/include
> 
>    # make is in the directory /usr/bin not in /bin
>    MAKE = /usr/bin/make
> 
> 4. Compile the ARPACK­software and change the name of the created static
> library 
> libarpack_MAC.a into libarpack.a. Then move the renamed static library file
> into 
> the lib directory of Octave.app, eg.
> 
>    bash:~/ARPACK$ make lib
>    bash:~/ARPACK$ mv libarpack_MAC.a libarpack.a
>    bash:~/ARPACK$ mv libarpack.a
> /Applications/Octave.app/Contents/Resources/lib
> 
> 5. Startup Octave.app and install the desired Octave­package, eg.
> 
>    octave-2.9.16:1> pkg install arpack-1.0.2.tar.gz
> _______________________________________________

Thomas,
This almost worked for me but I don't have eigs.m only svds.m.
Henry

[~/ARPACK] -bash-2.05b 511$ locate eigs.m

 [~/ARPACK] -bash-2.05b 512$ ls
ARMAKES         BLAS            EXAMPLES        Makefile        SRC
ARmake.inc      DOCUMENTS       LAPACK          README          UTIL

 [~/ARPACK] -bash-2.05b 513$ locate svds.m
/Users/hfm/octave/arpack-1.0.2/svds.m

 [~/ARPACK] -bash-2.05b 514$ cd /Users/hfm/octave

 [~/octave] -bash-2.05b 515$ ls
arpack-1.0.2    odepkg-0.3.3    signal-1.0.4

 [~/octave] -bash-2.05b 516$ cd arpack-1.0.2

 [~/octave/arpack-1.0.2] -bash-2.05b 517$ ls
doc                                     powerpc-apple-darwin7.9.1-api-v29
packinfo                                svds.m

 [~/octave/arpack-1.0.2] -bash-2.05b 518$