help-octave
[Top][All Lists]
Advanced

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

Re: custom arpack linked with custom ATLAS and lapack not found by octav


From: Tatsuro MATSUOKA
Subject: Re: custom arpack linked with custom ATLAS and lapack not found by octave 3.2.0
Date: Fri, 26 Jun 2009 10:29:53 +0900 (JST)

Hello

Source of ARPACK is designed for f77 complier.

in UTIL/second.f
24:       EXTERNAL           ETIME

ETIME in gfortran is internal function.
This line should be commented out like
24:*       EXTERNAL           ETIME

I hope the above is helpful for you.

Regards

Tatsuro

--- Riccardo Corradini  wrote:

> Dear octave users,
> I have a problem both compiling octave 3.2.0 and 3.2.1rc1 when I try to tell 
> configure to detect
> arpack library
> here there is configure
> ./configure --prefix=/home/corradin/octave-3.2.0/ CFLAGS="-O2 -I
> /home/corradin/lib/suitesparse/include/" CXXFLAGS="-O2 -I
> /home/corradin/lib/suitesparse/include/" LDFLAGS="-lm -lgfortran -lpthread
> -L/home/corradin/lib/lapack/ -L/home/corradin/lib/arpack/ 
> -L/home/corradin/lib/atlas/lib/
> -L/home/corradin/lib/qrupdate -L/home/corradin/lib/suitesparse/lib " 
> --with-blas="-llapack
> -lptcblas -lptf77blas -latlas"
> If I exclude arpack from compilation everything goes fine
> Here there is Armake.inc of arpack
> 
> ###########################################################################
> #
> # Program: ARPACK
> #
> # Module: ARmake.inc
> #
> # Purpose: Top-level Definitions
> #
> # Creation date: February 22, 1996
> #
> # Modified:
> #
> # Send bug reports, comments or suggestions to address@hidden
> #
> ############################################################################
> #
> # %---------------------------------%
> # | SECTION 1: PATHS AND LIBRARIES |
> # %---------------------------------%
> #
> #
> # %--------------------------------------%
> # | You should change the definition of |
> # | home if ARPACK is built some place | 
> # | other than your home directory. |
> # %--------------------------------------%
> #
> home = $(HOME)/lib/arpack
> #
> # %--------------------------------------%
> # | The platform identifier to suffix to |
> # | the end of library names |
> # %--------------------------------------%
> #
> curdir = $(PWD)/. 
> #
> # %------------------------------------------------------%
> # | The directories to find the various pieces of ARPACK |
> # %------------------------------------------------------%
> #
> 
> UTILdir = $(PWD)/UTIL
> SRCdir = $(PWD)/SRC
> #
> #
> # %-------------------------------------------------------------------%
> # | Comment out the previous line and uncomment the following |
> # | if you already have the BLAS and LAPACK installed on your system. |
> # | NOTE: ARPACK assumes the use of LAPACK version 2 codes. |
> # %-------------------------------------------------------------------%
> #
> DIRS = $(UTILdir) $(SRCdir)
> #
> # %---------------------------------------------------%
> # | The name of the libraries to be created/linked to |
> # %---------------------------------------------------%
> #
> ARPACKLIB = $(HOME)/lib/arpack/libarpack.a
> LAPACKLIB = $(HOME)/lib/lapack/lapack.a
> BLASLIB = $(HOME)/lib/atlas/lib/liblapack.a 
> $(HOME)/lib/atlas/lib/libptcblas.a
> $(HOME)/lib/atlas/lib/libptf77blas.a $(HOME)/lib/atlas/lib/libatlas.a
> 
> #
> ALIBS = $(ARPACKLIB) $(LAPACKLIB) $(BLASLIB) 
> #
> # 
> # %---------------------------------------------------------%
> # | SECTION 2: COMPILERS |
> # | |
> # | The following macros specify compilers, linker/loaders, |
> # | the archiver, and their options. You need to make sure |
> # | these are correct for your system. |
> # %---------------------------------------------------------%
> #
> #
> # %------------------------------%
> # | Make our own suffixes' list. |
> # %------------------------------%
> #
> .SUFFIXES:
> .SUFFIXES: .f .o
> #
> # %------------------%
> # | Default command. |
> # %------------------%
> #
> .DEFAULT:
>  @$(ECHO) "Unknown target $@, try: make help"
> #
> # %-------------------------------------------%
> # | Command to build .o files from .f files. |
> # %-------------------------------------------%
> #
> .f.o:
>  @$(ECHO) Making $@ from $<
>  @$(FC) -c $(FFLAGS) $<
> #
> # %-----------------------------------------%
> # | Various compilation programs and flags. |
> # | You need to make sure these are correct |
> # | for your system. |
> # %-----------------------------------------%
> #
> FC = gfortran
> FFLAGS = -O3 -fexceptions -fPIC -m64
> 
> LDFLAGS = -lm -lgfortran -lgfortranbegin -lpthread $(ALIBS)
> CD = cd
> 
> ECHO = echo
> 
> LN = ln
> LNFLAGS = -s
> 
> MAKE = make
> 
> RM = rm
> RMFLAGS = -f
> 
> SHELL = /bin/sh
> #
> # %----------------------------------------------------------------%
> # | The archiver and the flag(s) to use when building an archive |
> # | (library). Also the ranlib routine. If your system has no |
> # | ranlib, set RANLIB = touch. |
> # %----------------------------------------------------------------%
> #
> AR = ar 
> ARFLAGS = rv
> #RANLIB = touch
> RANLIB = ranlib
> #
> # %----------------------------------%
> # | This is the general help target. |
> # %----------------------------------%
> #
> help:
>  @$(ECHO) "usage: make ?"
> 
> I don't understand what's wrong, because lapack and ATLAS go very well on 
> octave's test ( make
> check).
> Thanks a lot for all your patience and help
> Bests
> Riccardo 
> 
> 
> 
> 
> 
>       > _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
> 


--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/


reply via email to

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