custom arpack linked with custom ATLAS and lapack not found by octave 3.2.0
Riccardo Corradini
riccardocorradini at yahoo.it
Fri Jun 26 05:21:15 CDT 2009
When I run make check I have just one fail for svds
This is the relevant part of fntests.log
>>>>> processing /home/corradin/d1/packaging/octave-3.2.0/scripts/sparse/svds.m
***** testif HAVE_ARPACK
[u2,s2,v2,flag] = svds(a,k,0);
s2 = diag(s2);
assert(flag,!1);
assert(s(k:-1:1), s2, 1e-10);
!!!!! test failed
assert (flag,!1) expected
0
but got
1
values do not match>>>>> processing /home/corradin/d1/packaging/octave-3.2
Thanks to all
Bests
Riccardo
--- Ven 26/6/09, Riccardo Corradini <riccardocorradini at yahoo.it> ha scritto:
Da: Riccardo Corradini <riccardocorradini at yahoo.it>
Oggetto: Re: custom arpack linked with custom ATLAS and lapack not found by octave 3.2.0
A: "Jaroslav Hajek" <highegg at gmail.com>
Cc: help-octave at octave.org
Data: Venerdì 26 giugno 2009, 10:37
Dear Tatsuro and Jaroslav,
Now configure works properly after Tatsuro's modification ( i forgot to delete an old larpack.so in /home/corradin/lib/arpack .. now there is only the upgraded libarpack.a)
I will tell you as possible if there are any problems with eigs test and svd tests.
Thanks a lot
Riccardo
--- Ven 26/6/09, Jaroslav Hajek <highegg at gmail.com> ha scritto:
Da: Jaroslav Hajek <highegg at gmail.com>
Oggetto: Re: custom arpack linked with custom ATLAS and lapack not found by octave 3.2.0
A: "Riccardo Corradini" <riccardocorradini at yahoo.it>
Cc: help-octave at octave.org
Data: Venerdì 26 giugno 2009, 06:52
On Thu, Jun 25, 2009 at 10:43 AM,
Riccardo
Corradini<riccardocorradini at yahoo.it> 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 arpack at caam.rice.edu
> #
> ############################################################################
> #
> # %---------------------------------%
> # | 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
>
>
>
>
And what error are you getting?
--
RNDr. Jaroslav
Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
-----Segue allegato-----
_______________________________________________
Help-octave mailing list
Help-octave at octave.org
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www-old.cae.wisc.edu/pipermail/help-octave/attachments/20090626/8051fb25/attachment-0001.html
More information about the Help-octave
mailing list