lapackpp-devel — Discussion of Lapack++ development

Re: [Lapackpp-devel] question of including lapack++ in my makefile

[Dee <de...@de...>]

Hello,

you forgot to link the Lapack-library in your Makefile. Please see
chapter "Library Usage" on http://lapackpp.sourceforge.net/

With regards
Dominik


-------- Original-Nachricht --------
Betreff: [Lapackpp-devel] question of including lapack++ in my makefile
Von: Abraham Chang-Tsan Lu <cha...@cm...>
An: lap...@li...
Datum: 12.11.2011 00:18

> Dear Lapack++ Developer,
> 
> I have some trouble in including lapack++ in my makefile.
> 
> On my machine, Lapack++ is under the directory of
> /home/changtsl/lapackpp-2.5.4
> and
> /home/changtsl/lapackpp_lib.
> 
> I have attached my code, makefile, and the error message given in the
> terminal. The code is very short and only for testing. Would you please
> help me to solve the problem? Thank you very much.
> 
> Sincerely,
> changtsan
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> 
> 
> 
> _______________________________________________
> lapackpp-devel mailing list
> lap...@li...
> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel

[Lapackpp-devel] question of including lapack++ in my makefile

[Abraham Chang-T. L. <cha...@cm...>]

Dear Lapack++ Developer,

I have some trouble in including lapack++ in my makefile.

On my machine, Lapack++ is under the directory of
/home/changtsl/lapackpp-2.5.4
and
/home/changtsl/lapackpp_lib.

I have attached my code, makefile, and the error message given in the
terminal. The code is very short and only for testing. Would you please
help me to solve the problem? Thank you very much.

Sincerely,
changtsan

-- 
Abraham Chang-Tsan Lu
Civil and Environmental Engineering
Carnegie Mellon University
Pittsburgh, PA, 15213

[Lapackpp-devel] Make check error

[hadi k. <had...@gm...>]

Hi

I have installed lapackpp-2.5.3 under Ubuntu11.04. The main steps
./configure, make and make install went well seemingly but when
"make check" I got these errors :

make[3]: Warning: File `.deps/tblasd++.Po' has modification time 1.9e+08 s
in the future
if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include
-I../../include -DLA_COMPLEX_SUPPORT -DLinux     -g -O2 -Wall -MT tblasd++.o
-MD -MP -MF ".deps/tblasd++.Tpo" -c -o tblasd++.o tblasd++.cc; \
    then mv -f ".deps/tblasd++.Tpo" ".deps/tblasd++.Po"; else rm -f
".deps/tblasd++.Tpo"; exit 1; fi
tblasd++.cc: In function ‘int main(int, char**)’:
tblasd++.cc:61:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:61:57: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:74:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:75:26: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:93:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:93:60: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:101:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:101:47: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:113:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:113:59: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:128:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:128:54: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:143:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:143:50: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:163:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:163:57: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:176:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:177:26: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:199:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:199:62: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:210:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:210:47: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:222:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:222:59: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:237:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:237:54: error: ‘fprintf’ was not declared in this scope
tblasd++.cc:252:13: error: ‘stdout’ was not declared in this scope
tblasd++.cc:252:50: error: ‘fprintf’ was not declared in this scope
make[3]: *** [tblasd++.o] Error 1
make[3]: Leaving directory `/home/hadi/lapackpp-2.5.3/blaspp/testing'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/hadi/lapackpp-2.5.3/blaspp/testing'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/hadi/lapackpp-2.5.3/blaspp'
make: *** [check-recursive] Error 1

I am a noob in this area. Please help me fix it. Also I have attached
config.log file though it seems perfect.
(I need lapackpp to use within  OBOE <https://projects.coin-or.org/OBOE/>)

Regards
H.Karimi

Re: [Lapackpp-devel] @lapack-devel, strange errors in header inclusion

[Curtis K. <ck...@ud...>]

Never mind, all issues resolved.  Sorry to bother you.

On Mon, Jul 11, 2011 at 3:57 PM, Curtis Kisielius <ck...@ud...> wrote:

> Hi,
>
> I'm an aspiring lapack++ user with what I hope is a simple question.
>
> My OS is ubuntu 9.10.  I had a seemingly successful installation of
> lapack++ v2.5.4, using ./configure, then make, then make install.  It passed
> the included test.
>
> My problem was mentioned, but not resolved, on forums.  When I try to
> compile this simple program:
> #include <iostream>
> #include <lapackpp/lapackpp.h>
> using namespace std;
> int main(){
> //cout << "this should print" << endl;
> return 0;
> }
>
> I get the following error:
> curtis@box-laptop:~/Desktop$ g++ lapack++Demo.cpp
> In file included from /usr/local/include/lapackpp/
> lapackc.h:14,
>                  from /usr/local/include/lapackpp/lapack.h:10,
>                  from /usr/local/include/lapackpp/lapackpp.h:16,
>                  from myProgram.cpp:2:
> /usr/local/include/lapackpp/lacomplex.h:45:23: error: laversion.h: No such
> file or directory
> /usr/local/include/lapackpp/lacomplex.h:48:17: error: f2c.h: No such file
> or directory
> In file included from /usr/local/include/lapackpp/lapackpp.h:47,
>                  from lapack++Demo.cpp:11:
> /usr/local/include/lapackpp/latmpl.h:36:22: error: lafnames.h: No such file
> or directory
>
> Which is strange because when I go to the /usr/local/include/lapackpp/
> directory, I can list all of those "missing" files.
>
>
> Another strange note:  There seems to be a workaround in typing: g++
> fileName.cpp -I /usr/local/include/lapackpp/
> With only the print statement in main, it compiles and runs, seemingly no
> longer having a problem with the #include.
> However, if I try to use any form of the LaGenMatDouble constructor other
> than the no-parameters version, the compiler insists that my references to
> the constructor (and destructor) are undefined.
>
> Could you shed any light on this issue, please?
>
> Thank you for your time,
> Curtis
>

[Lapackpp-devel] @lapack-devel, strange errors in header inclusion

[Curtis K. <ck...@ud...>]

Hi,

I'm an aspiring lapack++ user with what I hope is a simple question.

My OS is ubuntu 9.10.  I had a seemingly successful installation of lapack++
v2.5.4, using ./configure, then make, then make install.  It passed the
included test.

My problem was mentioned, but not resolved, on forums.  When I try to
compile this simple program:
#include <iostream>
#include <lapackpp/lapackpp.h>
using namespace std;
int main(){
//cout << "this should print" << endl;
return 0;
}

I get the following error:
curtis@box-laptop:~/Desktop$ g++ lapack++Demo.cpp
In file included from /usr/local/include/lapackpp/
lapackc.h:14,
                 from /usr/local/include/lapackpp/lapack.h:10,
                 from /usr/local/include/lapackpp/lapackpp.h:16,
                 from myProgram.cpp:2:
/usr/local/include/lapackpp/lacomplex.h:45:23: error: laversion.h: No such
file or directory
/usr/local/include/lapackpp/lacomplex.h:48:17: error: f2c.h: No such file or
directory
In file included from /usr/local/include/lapackpp/lapackpp.h:47,
                 from lapack++Demo.cpp:11:
/usr/local/include/lapackpp/latmpl.h:36:22: error: lafnames.h: No such file
or directory

Which is strange because when I go to the /usr/local/include/lapackpp/
directory, I can list all of those "missing" files.


Another strange note:  There seems to be a workaround in typing: g++
fileName.cpp -I /usr/local/include/lapackpp/
With only the print statement in main, it compiles and runs, seemingly no
longer having a problem with the #include.
However, if I try to use any form of the LaGenMatDouble constructor other
than the no-parameters version, the compiler insists that my references to
the constructor (and destructor) are undefined.

Could you shed any light on this issue, please?

Thank you for your time,
Curtis

[Lapackpp-devel] how to build for win7 / 64

[Rudolf P. <po...@uc...>]

I have a project using lapackpp under windows xp/32 but need to port it 
to windows 7 / 64. I am using VS2008 and no MinGW.

The mailing list seems to contain one person asking this previously 
(https://sourceforge.net/mailarchive/message.php?msg_id=24736456) and 
one person suggesting they had found a solution 
(https://sourceforge.net/mailarchive/message.php?msg_id=24220896) but 
not sharing the solution.

Is there a known way to achieve this? In fact, is there a good way to 
build lapackpp without first installing the lapackpp-2.5.1 exe version?

So far I have tried downloading the libraries from the lapack site 
directly (even if that set is named lapack.lib and blas.lib) but this 
leads to link errors as outlined by 
https://sourceforge.net/mailarchive/message.php?msg_id=24736456:

Finished searching libraries
blas1pp.obj : error LNK2019: unresolved external symbol _dasum_ 
referenced in function "double __cdecl Blas_Norm1(class LaVectorDouble 
const &)" (?Blas_Norm1@@YANABVLaVectorDouble@@@Z)
blas1pp.obj : error LNK2019: unresolved external symbol _daxpy_ 
referenced in function "void __cdecl Blas_Add_Mult(class LaVectorDouble 
&,double,class LaVectorDouble const &)" 
(?Blas_Add_Mult@@YAXAAVLaVectorDouble@@NABV1@@Z)
blaspp.obj : error LNK2001: unresolved external symbol _daxpy_
...

Grateful for any pointers,

   Rudolf

Re: [Lapackpp-devel] Compiling LaPack++ on TACC Ranger

[Christian S. <sti...@tu...>]

Dear Craig,

thanks for your interest and your well-thought questions. Unfortunately I 
don't work with lapack++ anymore, so for the most part I can't really help 
here, except for two of your questions below. Also, I don't know about TACC at 
all but it's an interesting use case :-)

Am Mittwoch, 15. Juni 2011 schrieb Craig Jolley:
> Hi... I've been using LaPack++ for a while on my laptop machine, and I'm
> now trying to parallelize my code and run it on the TACC Ranger cluster (
> http://www.tacc.utexas.edu/resources/hpc/#constellation).  Unfortunately,
> I'm running into some trouble -- I've tried building it using GCC, Intel,
> and PGI compiler sets and they all run into different problems.  I've also
> contacted the TACC staff about this (I'm cc-ing the person I've been
> talking to on this e-mail), but I thought that you might have some
> experience with running LaPack++ in HPC environments, or at least with
> using different compilers.  In case you're wondering, I don't plan on
> parallelizing the actual matrix calculations -- my code will be
> diagonalizing a large number of fairly small matrices, so each matrix
> operation will only be running on a single CPU.
> 
> ***********************
> 
> The PGI compiler fails while I'm trying to run "make", with the following
> error:
> 
> libtool: compile:  pgCC -DHAVE_CONFIG_H -I. -I.. -I../include -I../include
> -I../include -DLA_COMPLEX_SUPPORT -DLinux -g -c genmd.cc  -fpic -DPIC -o
> .libs/genmd.o
> "genmd.cc", line 68: error: exception specification is incompatible with
> that
>           of previous function "drand48" (declared at line 508 of
>           "/usr/include/stdlib.h")
>   extern "C" double drand48(void) throw ();
> 
> It's not clear to me what this error is all about -- is there anything
> special I need to do when compiling LaPack++ using the PGI suite?

In src/genmd.cc line 68 you can safely remove the trailing "throw()" from the 
declaration of drand48. This should get rid of this error. In SVN, I've also 
remove that throws-clause. I thought the prototype of drand48() were 
standarized, including its exception specification aka throws-clause (even 
though in C++ the exception specification is almost useless anyway), but 
apparently this is not the case. Hence, that workaround of a local declaration 
of drand48 should simply be changed to not contain any throws-clause.

> ***********************
> 
> When I build in the GCC environment, configure and make work fine, but
> "make check" fails with the following error:
> 
> libtool: link: g++ -g -O2 -Wall -o .libs/tblasd++ tblasd++.o
> ../../src/.libs/liblapackpp.so -Wl,-rpath
> -Wl,/share/home/01055/tg803190/lapackpp/lib
> /opt/apps/gcc4_4/atlas/3.9.32/lib/libatlas.so: undefined reference to
> `pthread_attr_setaffinity_np'
> 
> I've tried adding the environment CFLAGS=pthread and LDFLAGS=pthread when I
> run configure (based on what I understood from
> http://www.kernel.org/doc/man-pages/online/pages/man3/pthread_attr_setaffin
> ity_np.3.html), but then LaPack++ won't compile at all.

If you want to have lapackp++ be linking against libpthread, you shouldn't 
modify CFLAGS and you should set LDFLAGS=-lpthread (your setting was missing 
the preceding "-l", a minus and a lower-case ell character). This should work 
with gcc and should probably fix the undefined-reference error.

> ***********************
> 
> Finally, when I build using Intel compilers, configure and make run
> properly, but then "make check" gives me a bunch of lines that look like:
> 
> ld: Dwarf Error: mangled line number section (bad file number).
> 
> followed by a whole slew of "undefined reference" errors, all of them to
> things in the std namespace.  I'm not sure what a "dwarf error" is, but
> this looks like a linking problem.  Is there something special that I need
> to do when building LaPack++ with Intel compilers?  I used the CXX=icc,
> CC=icc, F77=ifort, and FC=ifort environment variables with "configure";
> compilation failed when I tried using CXX=icpc instead.

I have no idea about this error. It is a linking problem, yes, but this sort 
of problem rather shows up if the compiler tools have been mixed-up between 
different compilers. I.e. this error might occur if you have some object files 
compiled with gcc's compiler but which are now being linked with the Intel 
linker. Or vice versa: Maybe you correctly chose Intel compiler but didn't 
choose Intel's linker by setting LD=ild or something similar.

> I know this is a lot of problems all at once and you probably aren't
> familiar with the details of the TACC Ranger setup, but if you've had any
> similar experiences with these compiler sets it could help me get this
> resolved a lot more quickly.
> 
> Thank you for taking the time to look at this.

No experiences from my side, but those guesses as outlined above. Feel free to 
ask more questions, especially those well-thought and precise ones as above 
:-) and I'll see what I can help.

Best Regards,

Christian

Re: [Lapackpp-devel] Installation of Lapack++ for windows using Visual C ++

[Yassine K. <yas...@gm...>]

I have the lapack dll compiled with visual studio 2008. if interested i can
send it to you, just need to link it to your project and should work. please
let me know.

-Yassine

On Tue, May 3, 2011 at 5:02 AM, DENIS Pierre (EXT)
<Pie...@so...>wrote:

> Hello,
>
> I am trying to install Lapack++ on windows for visual c ++(2010).
>
> I have downloaded lapack++ v2.5.4 and the installer exe setup package.
>
> The exe setup works correctly and install LIBBLAS32.DLL, LIBLAPACK32.DLL
> in C:WINDOWS.
> I am trying to follow the instruction of Lapack++ v2.5.2 API Documentation.
> In requirement section, It is written that This package requires the
> packages "blas", "lapack" (without the "++"), and a Fortran compiler. Does
> it apply to windows installation, the document doesn’t mention them in the
> section Compile and Install? Moreover, the document mention the use of LIBBLAS32.DLL
> and LIBLAPACK32.DLL (are these files the output of compiling blas and lapack
> on windows ?)   Here is what I have done from my understanding of the
> document:I compiled the VC++ project (there are in fact 6 underprojects in
> the solution, do I need to execute all the project? with a link to the two
> libraries  LIBBLAS32.DLL and LIBLAPACK32.DLL (the one generated by the
> install exe. I put a link only for the  librairies  .lib in the project.But
> when I want to compile it , I get an error.I do not understand what is
> wrong in my proceed.Attached is the buildlog of the execution . Thanks in
> advance for your help, I have tried to check in documentation but I am
> novice in library use so I mayNot interpret correctly some explanations of
> the user doc.
>
>
> =========================================================
>
> Ce message et toutes les pieces jointes (ci-apres le "message")
> sont confidentiels et susceptibles de contenir des informations
> couvertes par le secret professionnel. Ce message est etabli
> a l'intention exclusive de ses destinataires. Toute utilisation
> ou diffusion non autorisee interdite.
> Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE
> et ses filiales declinent toute responsabilite au titre de ce message
> s'il a ete altere, deforme falsifie.
>
> =========================================================
>
> This message and any attachments (the "message") are confidential,
> intended solely for the addressees, and may contain legally privileged
> information. Any unauthorised use or dissemination is prohibited.
> E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any
> of its subsidiaries or affiliates shall be liable for the message
> if altered, changed or falsified.
>
> =========================================================
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> lapackpp-devel mailing list
> lap...@li...
> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel
>
>

[Lapackpp-devel] Installation of Lapack++ for windows using Visual C ++

[DENIS P. (EXT) <Pie...@so...>]

ÿþ<

Re: [Lapackpp-devel] FW: Windows Mobile 5.0

[Christian S. <sti...@tu...>]

Zitat von Scott Graybill <Sco...@tr...>:
> I am trying to build LAPACK++  for use on Windows Mobile 5.0.  I changed
> the pre-processor definitions to:
>
>
> I am getting the following errors.  I think it's because the .exe setup
> package containing the auxiliary libraries, LIBBLAS32.LIB;
> LIBLAPACK32.Lib; LIBBLAS32.DLL; and LIBLAPACK32.DLL, is built for WIN32.
> Does anybody know if this is correct?  I've looked for versions of these
> files built for Windows Mobile 5.0 but can't find anything.  Any ideas
> or thoughts would be greatly appreciated.
>
> Error      1              error LNK2019: unresolved external symbol
> dasum_ referenced in function "double __cdecl Blas_Norm1(class
> LaVectorDouble const &)" (?Blas_Norm1@@YANABVLaVectorDouble@@@Z)
> blas1pp.obj                lapackpp

Sure, this is because of an unsuitable LIBLAPACK32.DLL and  
LIBBLAS32.DLL. You need to build those by yourself as well. The  
explanation on how to do that is in  
http://lapackpp.svn.sourceforge.net/viewvc/lapackpp/lapackpp/trunk/contrib/README?revision=291&view=markup and the README.W32 in the top source dir. Sorry, I can't help with any further details because I'm no longer active here,  
though.

Regards,

Christian

[Lapackpp-devel] FW: Windows Mobile 5.0

[Scott G. <Sco...@tr...>]

Hi,

 

I am trying to build LAPACK++  for use on Windows Mobile 5.0.  I changed
the pre-processor definitions to:

 

$(ARCHFAM)

$(_ARCHFAM_)

_WIN32_WCE=$(CEVER)

BUILDING_LAPACK_DLL

LA_COMPLEX_SUPPORT

 

I am getting the following errors.  I think it's because the .exe setup
package containing the auxiliary libraries, LIBBLAS32.LIB;
LIBLAPACK32.Lib; LIBBLAS32.DLL; and LIBLAPACK32.DLL, is built for WIN32.
Does anybody know if this is correct?  I've looked for versions of these
files built for Windows Mobile 5.0 but can't find anything.  Any ideas
or thoughts would be greatly appreciated.

 

Error      1              error LNK2019: unresolved external symbol
dasum_ referenced in function "double __cdecl Blas_Norm1(class
LaVectorDouble const &)" (?Blas_Norm1@@YANABVLaVectorDouble@@@Z)
blas1pp.obj                lapackpp

Error      2              error LNK2019: unresolved external symbol
daxpy_ referenced in function "void __cdecl Blas_Add_Mult(class
LaVectorDouble &,double,class LaVectorDouble const &)"
(?Blas_Add_Mult@@YAXAAVLaVectorDouble@@NABV1@@Z)   blas1pp.obj
lapackpp

Error      3              error LNK2001: unresolved external symbol
daxpy_        blaspp.obj           lapackpp

Error      4              error LNK2019: unresolved external symbol
dcopy_ referenced in function "void __cdecl Blas_Copy(class
LaVectorDouble const &,class LaVectorDouble &)"
(?Blas_Copy@@YAXABVLaVectorDouble@@AAV1@@Z)      blas1pp.obj
lapackpp

Error      5              error LNK2001: unresolved external symbol
dcopy_        dtimmg.obj        lapackpp

Error      6              error LNK2019: unresolved external symbol
ddot_ referenced in function "double __cdecl Blas_Dot_Prod(class
LaVectorDouble const &,class LaVectorDouble const &)"
(?Blas_Dot_Prod@@YANABVLaVectorDouble@@0@Z)    blas1pp.obj
lapackpp

Error      7              error LNK2001: unresolved external symbol
ddot_           blas3pp.obj        lapackpp

Error      8              error LNK2001: unresolved external symbol
ddot_           blaspp.obj           lapackpp

Error      9              error LNK2019: unresolved external symbol
dnrm2_ referenced in function "double __cdecl Blas_Norm2(class
LaVectorDouble const &)" (?Blas_Norm2@@YANABVLaVectorDouble@@@Z)
blas1pp.obj                lapackpp

Error      10           error LNK2019: unresolved external symbol drot_
referenced in function "void __cdecl Blas_Apply_Plane_Rot(class
LaVectorDouble &,class LaVectorDouble &,double &,double &)"
(?Blas_Apply_Plane_Rot@@YAXAAVLaVectorDouble@@0AAN1@Z)
blas1pp.obj        lapackpp

 

Scott Graybill | R&D Specialist | Trimble Navigation NZ Ltd.

11 Birmingham Drive, PO Box 8729, Riccarton, Christchurch, 8440, New
Zealand

P: +64 3 963 5494 | E:  sco...@tr...

 

[Lapackpp-devel] Support for Windows Mobile applications

[Scott G. <sco...@tr...>]

Hi,

 

I've successfully built the lapacpp project in both WIN32 debug and
release mode with MSVS 2008.  It works beautifully.  I was having a lot
of problems using LAPACK.  However, I get a lot of errors when I try to
build in both Windows Mobile 5.0 Pocket PC SDK debug and release mode.
Is there support for this?

 

Cheers,

 

Scott

 

 

Scott Graybill | R&D Specialist | Trimble Navigation NZ Ltd.

11 Birmingham Drive, PO Box 8729, Riccarton, Christchurch, 8440, New
Zealand

P: +64 3 963 5494 | E:  sco...@tr...

 

Re: [Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Dr.Peer-Joachim K. <pk...@bg...>]

Hi,

I found the problem. I've installed the SLES blas and lapack
packages. Finally I tried to build everything (blas, lapack,atlas).
Now everything works !


Thanks and bye, Peer

Am 04.11.2010 11:26, schrieb Christian Stimming:
> Hi,
>
> Zitat von "Dr.Peer-Joachim Koch" <pk...@bg...>:
>> First step was to install the SLES BLAS and LAPACK rpms.
>>
>> rpm -ql lapack-3.0-939.4 blas-3.0-939.4
>> /usr/lib64/liblapack.a
>> /usr/lib64/liblapack.so.3.0.0
>> /usr/lib64/libtmglib.a
>> /usr/share/doc/packages/lapack
>> /usr/share/doc/packages/lapack/README
>> /usr/lib64/libblas.a
>> /usr/lib64/libblas.so
>> /usr/lib64/libblas.so.3
>> /usr/lib64/libblas.so.3.0.0
>
> ok, thanks, I see the shared liblapack.so is there. Then I would guess
> this might be due to the old ./configure shell script in the downloaded
> lapackpp.tar.gz - maybe the version of autoconf that created the
> ./configure script cannot recognize the shared lapack.so on your system
> (anymore). Can you try the SVN version?
>
> svn co
> https://lapackpp.svn.sourceforge.net/svnroot/lapackpp/lapackpp/trunk
> lapackpp
> cd lapackpp
> ./autogen.sh
>
> and then continue with ./configure;make as usual. Maybe the autotool
> versions on your system will then pick up the shared liblapack.so
> correctly and all is fine again.
>
> Having said that, I currently don't work with lapackpp anymore and I
> haven't been working with it for quite some time by now.
> http://www.cuvillier.de/flycms/de/html/30/-UickI3zKPS7zc0k=/Buchdetails.html
>
> Hence it is very well possible that the last released version doesn't
> immediately compile on the most recent distributions. I will happily
> assist to get it working again, or to add more developers to the
> sourceforge site so that others can commit bugfixes and improvements to
> SVN, but I have to say clearly that currently I'm not using this myself.
> (I used to use it heavily in 2006-2008, though.)
>
> Best Regards,
>
> Christian
>
>


-- 
Mit freundlichem Gruß
     Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10            Telefon: ++49 3641 57-6705
D-07745 Jena                 Telefax: ++49 3641 57-7705

Re: [Lapackpp-devel] Lapack++ Memory Limitations

[Christian S. <sti...@tu...>]

Dear Donna,

please ask on the mailing list lap...@li... (already 
in CC). I personally haven't been using lapackpp for quite some time by now.

As for large matrices and LAPACK (the underlying one, without pp): No, I have 
no information about its implicit size limits. Your 5000x5000 double example 
corresponds to  approx. 200 MByte of memory, which sounds still reasonable for 
today's amounts of RAM that people have. I thought people have reported before 
that somewhat larger matrices also work, but I'm not sure. I haven't worked 
with such large matrices before.

Also, I have no information about debugging aids in LAPACK. Sorry for that.

Regards,

Christian

Am Donnerstag, 4. November 2010 schrieb dd...@vo...:
> Hi Mr. Stimming,
> 
> I am a software engineer, and I have been using Lapack++ to solve large
> linear systems for my work, but have been finding that some operations
> fail (basic addition, multiplication, and calls to "LaLinearSolve") if I
> use matrices that are too large (on the order of 5000x5000 doubles, give
> or take).  I found your email off of the Lapack++ documentation website,
> so I thought I'd contact you about the problem.
> 
> I was wondering if you knew where I could find more information about what
> the hard matrix size limits are, and if there are any work-arounds for
> this. I would look into the memory limitations of the underlying BLAS
> library, but it wasn't clear to me which functions from this library were
> being called. Perhaps there is some discussion group or thread focusing on
> this topic?
> 
> Also, does Lapack have any error/debugging support so I can determine
> details about thrown exceptions, etc. ?
> 
> Thanks very much for your help!
> 
> Sincerely,
> 
> Donna Dupuis
> Software Development Engineer
> Vorum Research Corporation
> Vancouver, BC

Re: [Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Dr.Peer-Joachim K. <pk...@bg...>]

Hi,

also svn stuff fails. I also tried to use the
src.rpm+tarball. Same fault.
You're rpm (opensuse) looks for blas.so.3.1.0
but we've only blas.so.3.0.0.


I also tried to use the pgi compiler. Here everything
seemed to be build. However the check fails, because
the libla*.so is pointing to nowhere ....


-rw-r--r-- 1 pkoch AG_DV  27400 2010-11-04 13:08 dopla.o
-rw-r--r-- 1 pkoch AG_DV  19296 2010-11-04 13:08 dtimmg.o
-rw-r--r-- 1 pkoch AG_DV 276168 2010-11-04 13:08 eigslv.o
-rw-r--r-- 1 pkoch AG_DV 260864 2010-11-04 13:08 genmd.o
-rw-r--r-- 1 pkoch AG_DV   5624 2010-11-04 13:08 laprefs.o
-rw-r--r-- 1 pkoch AG_DV 402528 2010-11-04 13:08 lasvd.o
-rw-r--r-- 1 pkoch AG_DV 227968 2010-11-04 13:08 lautil.o
lrwxrwxrwx 1 pkoch AG_DV     17 2010-11-04 13:08 liblapackpp.la -> 
../liblapackpp.la
-rw-r--r-- 1 pkoch AG_DV   1091 2010-11-04 13:08 liblapackpp.lai
lrwxrwxrwx 1 pkoch AG_DV     21 2010-11-04 13:08 liblapackpp.so -> 
liblapackpp.so.14.2.0
lrwxrwxrwx 1 pkoch AG_DV     21 2010-11-04 13:08 liblapackpp.so.14 -> 
liblapackpp.so.14.2.0
-rw-r--r-- 1 pkoch AG_DV 347560 2010-11-04 13:08 linslv.o
-rw-r--r-- 1 pkoch AG_DV   3272 2010-11-04 13:08 systime.o



The liblapackpp.so.14.2.0 is missing ...

Thanks a lot for you help!

Bye, Peer


Am 04.11.2010 11:26, schrieb Christian Stimming:
> Hi,
>
> Zitat von "Dr.Peer-Joachim Koch" <pk...@bg...>:
>> First step was to install the SLES BLAS and LAPACK rpms.
>>
>> rpm -ql lapack-3.0-939.4 blas-3.0-939.4
>> /usr/lib64/liblapack.a
>> /usr/lib64/liblapack.so.3.0.0
>> /usr/lib64/libtmglib.a
>> /usr/share/doc/packages/lapack
>> /usr/share/doc/packages/lapack/README
>> /usr/lib64/libblas.a
>> /usr/lib64/libblas.so
>> /usr/lib64/libblas.so.3
>> /usr/lib64/libblas.so.3.0.0
>
> ok, thanks, I see the shared liblapack.so is there. Then I would guess
> this might be due to the old ./configure shell script in the downloaded
> lapackpp.tar.gz - maybe the version of autoconf that created the
> ./configure script cannot recognize the shared lapack.so on your system
> (anymore). Can you try the SVN version?
>
> svn co
> https://lapackpp.svn.sourceforge.net/svnroot/lapackpp/lapackpp/trunk
> lapackpp
> cd lapackpp
> ./autogen.sh
>
> and then continue with ./configure;make as usual. Maybe the autotool
> versions on your system will then pick up the shared liblapack.so
> correctly and all is fine again.
>
> Having said that, I currently don't work with lapackpp anymore and I
> haven't been working with it for quite some time by now.
> http://www.cuvillier.de/flycms/de/html/30/-UickI3zKPS7zc0k=/Buchdetails.html
>
> Hence it is very well possible that the last released version doesn't
> immediately compile on the most recent distributions. I will happily
> assist to get it working again, or to add more developers to the
> sourceforge site so that others can commit bugfixes and improvements to
> SVN, but I have to say clearly that currently I'm not using this myself.
> (I used to use it heavily in 2006-2008, though.)
>
> Best Regards,
>
> Christian
>
>


-- 
Mit freundlichem Gruß
     Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10            Telefon: ++49 3641 57-6705
D-07745 Jena                 Telefax: ++49 3641 57-7705

Re: [Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Christian S. <sti...@tu...>]

Zitat von "Dr.Peer-Joachim Koch" <pk...@bg...>:
> Building with pgi (all compilers) "seems" to work, but there is now
> shared lib created, just the static one.

The lapackpp (with pp) needs to link against an existing LAPACK  
(without pp) library. In your case, you seem to have the LAPACK  
library installed only in the static version:

> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a(dgeev.i): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with  
> -fPIC
> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a: could  
> not read symbols: Bad value

You cannot build a shared lapackpp (with pp) unless you also have a  
shared LAPACK installed. Install the shared LAPACK (resulting in some  
file liblapack.so, potentially with additional suffixes) and try again  
configure and make.

Does that fix the problem?

Gruß aus Hamburg nach Jena!

Christian

Re: [Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Christian S. <sti...@tu...>]

Hi,

Zitat von "Dr.Peer-Joachim Koch" <pk...@bg...>:
> First step was to install the SLES BLAS and LAPACK rpms.
>
> rpm -ql lapack-3.0-939.4 blas-3.0-939.4
> /usr/lib64/liblapack.a
> /usr/lib64/liblapack.so.3.0.0
> /usr/lib64/libtmglib.a
> /usr/share/doc/packages/lapack
> /usr/share/doc/packages/lapack/README
> /usr/lib64/libblas.a
> /usr/lib64/libblas.so
> /usr/lib64/libblas.so.3
> /usr/lib64/libblas.so.3.0.0

ok, thanks, I see the shared liblapack.so is there. Then I would guess  
this might be due to the old ./configure shell script in the  
downloaded lapackpp.tar.gz - maybe the version of autoconf that  
created the ./configure script cannot recognize the shared lapack.so  
on your system (anymore). Can you try the SVN version?

   svn co  
https://lapackpp.svn.sourceforge.net/svnroot/lapackpp/lapackpp/trunk  
lapackpp
   cd lapackpp
   ./autogen.sh

and then continue with ./configure;make as usual. Maybe the autotool  
versions on your system will then pick up the shared liblapack.so  
correctly and all is fine again.

Having said that, I currently don't work with lapackpp anymore and I  
haven't been working with it for quite some time by now.  
http://www.cuvillier.de/flycms/de/html/30/-UickI3zKPS7zc0k=/Buchdetails.html
Hence it is very well possible that the last released version doesn't  
immediately compile on the most recent distributions. I will happily  
assist to get it working again, or to add more developers to the  
sourceforge site so that others can commit bugfixes and improvements  
to SVN, but I have to say clearly that currently I'm not using this  
myself. (I used to use it heavily in 2006-2008, though.)

Best Regards,

Christian

Re: [Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Dr.Peer-Joachim K. <pk...@bg...>]

Hi Christian,

thanks for the quick response !

First step was to install the SLES BLAS and LAPACK rpms.

rpm -ql lapack-3.0-939.4 blas-3.0-939.4
/usr/lib64/liblapack.a
/usr/lib64/liblapack.so.3.0.0
/usr/lib64/libtmglib.a
/usr/share/doc/packages/lapack
/usr/share/doc/packages/lapack/README
/usr/lib64/libblas.a
/usr/lib64/libblas.so
/usr/lib64/libblas.so.3
/usr/lib64/libblas.so.3.0.0


Then a "tar zxf lap..."; configure; make.

The configure normaly reclaims the missing blas lib.

So any other idea ?

Danke schöne Grüße zurück an meine alte (kurze) Heimat ;)

Ciao, Peer



Am 04.11.2010 10:49, schrieb Christian Stimming:
> Zitat von "Dr.Peer-Joachim Koch" <pk...@bg...>:
>> Building with pgi (all compilers) "seems" to work, but there is now
>> shared lib created, just the static one.
>
> The lapackpp (with pp) needs to link against an existing LAPACK (without
> pp) library. In your case, you seem to have the LAPACK library installed
> only in the static version:
>
>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a(dgeev.i):
>> relocation R_X86_64_32 against `a local symbol' can not be used when
>> making a shared object; recompile with -fPIC
>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a:
>> could not read symbols: Bad value
>
> You cannot build a shared lapackpp (with pp) unless you also have a
> shared LAPACK installed. Install the shared LAPACK (resulting in some
> file liblapack.so, potentially with additional suffixes) and try again
> configure and make.
>
> Does that fix the problem?
>
> Gruß aus Hamburg nach Jena!
>
> Christian
>


-- 
Mit freundlichem Gruß
     Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10            Telefon: ++49 3641 57-6705
D-07745 Jena                 Telefax: ++49 3641 57-7705

[Lapackpp-devel] Problem building lapackpp under SLES10SP2 (X86_64)

[Dr.Peer-Joachim K. <pk...@bg...>]

Hi,

I just downloaded the source set the comipler to gcc, g++ and gfortran
made a configure and try to build it.
The linking step fails.
Everything was build with "-fPIC".

Any idea what's wrong ?

Building with pgi (all compilers) "seems" to work, but there is now
shared lib created, just the static one.

Bye, Peer




if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I. -I.. -I../include -I../include -I../include -DLA_COMPLEX_SUPPORT 
-DLinux     -g -O2   -Wall -MT systime.lo -MD -MP -MF 
".deps/systime.Tpo" -c -o systime.lo systime.c; \
then mv -f ".deps/systime.Tpo" ".deps/systime.Plo"; else rm -f 
".deps/systime.Tpo"; exit 1; fi
   gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include 
-I../include -DLA_COMPLEX_SUPPORT -DLinux -g -O2 -Wall -MT systime.lo 
-MD -MP -MF .deps/systime.Tpo -c systime.c  -fPIC -DPIC -o .libs/systime.o
/bin/sh ../libtool --tag=CXX --mode=link g++  -g -O2 -Wall   -o 
liblapackpp.la -rpath /usr/local/apps/lapackpp/2.5.3/lib -no-undefined 
-version-info 16:0:2  dopla.lo dtimmg.lo eigslv.lo genmd.lo laprefs.lo 
lasvd.lo lautil.lo linslv.lo systime.lo ../matrix/src/liblamatrixpp.la 
../blaspp/src/libblaspp.la -llapack -lblas 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64 
-L/lib/../lib64 -L/usr/lib/../lib64 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/lib 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../..  -lgfortran -lm -lgcc_s
g++ -shared -nostdlib 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/crti.o 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/crtbeginS.o  .libs/dopla.o 
.libs/dtimmg.o .libs/eigslv.o .libs/genmd.o .libs/laprefs.o 
.libs/lasvd.o .libs/lautil.o .libs/linslv.o .libs/systime.o 
-Wl,--whole-archive ../matrix/src/.libs/liblamatrixpp.a 
../blaspp/src/.libs/libblaspp.a -Wl,--no-whole-archive  -Wl,--rpath 
-Wl,/usr/lib64/gcc/x86_64-suse-linux/4.1.2 -Wl,--rpath 
-Wl,/usr/lib64/gcc/x86_64-suse-linux/4.1.2 -llapack -lblas 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64 
-L/lib/../lib64 -L/usr/lib/../lib64 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/lib 
-L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../.. -lgfortran 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/libstdc++.so -lm -lc -lgcc_s 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/crtendS.o 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/crtn.o 
-Wl,-soname -Wl,liblapackpp.so.14 -o .libs/liblapackpp.so.14.2.0
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: 
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a(dgeev.i): 
relocation R_X86_64_32 against `a local symbol' can not be used when 
making a shared object; recompile with -fPIC
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64/liblapack.a: 
could not read symbols: Bad value
collect2: ld returned 1 exit status
make[2]: *** [liblapackpp.la] Fehler 1
make[2]: Leaving directory `/tmp/lapackpp-2.5.3/src'



-- 
Mit freundlichem Gruß
      Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10            Telefon: ++49 3641 57-6705
D-07745 Jena                 Telefax: ++49 3641 57-7705

Re: [Lapackpp-devel] Bug?

[Dee <de...@de...>]

I thought your program crashes? So how could you access the matrix
members? Or better how could be sure where it crashes? Further the
behaviour could be different on different systems.

If you use gcc please compile with the -g switch and run gdb to check
where the segfault appears.

Greetings
Dee


-------- Original-Nachricht --------
Betreff: Re: [Lapackpp-devel] Bug?
Von: Jan Korous <kor...@gm...>
An: Dee <de...@de...>
Datum: 18.09.2010 20:24

> That's strange. If I got bad_alloc, I would understand but I didn't.
> Matter of fact I can access most of the matrix members, even matrix (
> 25439, 25439 )...
> 
> Bad luck :-(
> 
> On Sat, Sep 18, 2010 at 7:10 PM, Dee <de...@de...> wrote:
>> Hello,
>>
>> I get this result:
>>
>> terminate called after throwing an instance of 'std::bad_alloc'
>>  what():  std::bad_alloc
>> Aborted
>>
>> The problem is in
>>
>> #5  0x00007ffff75c721e in __cxa_throw () from /usr/lib/libstdc++.so.6
>> #6  0x00007ffff75c76ad in operator new(unsigned long) () from
>> /usr/lib/libstdc++.so.6
>> #7  0x00007ffff75c7769 in operator new[](unsigned long) () from
>> /usr/lib/libstdc++.so.6
>> #8  0x00007ffff7bbfa19 in VectorDouble::VectorDouble(unsigned int) ()
>> from /usr/lib/liblapackpp.so.14
>> ---Type <return> to continue, or q <return> to quit---
>> #9  0x00007ffff7ba3761 in LaGenMatDouble::LaGenMatDouble(int, int) ()
>> from /usr/lib/liblapackpp.so.14
>> #10 0x0000000000400a87 in main () at lap.cpp:9
>>
>> So I suppose the resulting vector of size 647193600 is too big for the
>> stack (or heap).
>>
>> Greetings
>> Dee
>>
>>
>> -------- Original-Nachricht --------
>> Betreff: [Lapackpp-devel] Bug?
>> Von: Jan Korous <kor...@gm...>
>> An: lap...@li...
>> Datum: 18.09.2010 18:08
>>
>>> Hello,
>>> I intended to use Lapack++ in my CFD project for diploma thesis. But I
>>> found something stange. This simple code crashes, segfault...
>>>
>>> #include <stdio.h>
>>> #include <lapackpp/gmd.h> // LaGenMatDouble
>>>
>>> using namespace std;
>>> int main() {
>>>       LaGenMatDouble matrix ( 25440, 25440 );
>>>       cout << matrix(0, 8675);
>>>       return 0;
>>> }
>>>
>>> I don't know what's going on. I am using version 2.5.3 Are you able to
>>> reproduce the bug or is it just me?
>>>
>>> Thank you for your answer.
>>>
>>> Sincerely
>>> Jan Korous
>>>
>>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual appliances
>>> and start using them to simplify application deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>> _______________________________________________
>>> lapackpp-devel mailing list
>>> lap...@li...
>>> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel
> 

Re: [Lapackpp-devel] Bug?

[Jan K. <kor...@gm...>]

That's strange. If I got bad_alloc, I would understand but I didn't.
Matter of fact I can access most of the matrix members, even matrix (
25439, 25439 )...

Bad luck :-(

On Sat, Sep 18, 2010 at 7:10 PM, Dee <de...@de...> wrote:
> Hello,
>
> I get this result:
>
> terminate called after throwing an instance of 'std::bad_alloc'
>  what():  std::bad_alloc
> Aborted
>
> The problem is in
>
> #5  0x00007ffff75c721e in __cxa_throw () from /usr/lib/libstdc++.so.6
> #6  0x00007ffff75c76ad in operator new(unsigned long) () from
> /usr/lib/libstdc++.so.6
> #7  0x00007ffff75c7769 in operator new[](unsigned long) () from
> /usr/lib/libstdc++.so.6
> #8  0x00007ffff7bbfa19 in VectorDouble::VectorDouble(unsigned int) ()
> from /usr/lib/liblapackpp.so.14
> ---Type <return> to continue, or q <return> to quit---
> #9  0x00007ffff7ba3761 in LaGenMatDouble::LaGenMatDouble(int, int) ()
> from /usr/lib/liblapackpp.so.14
> #10 0x0000000000400a87 in main () at lap.cpp:9
>
> So I suppose the resulting vector of size 647193600 is too big for the
> stack (or heap).
>
> Greetings
> Dee
>
>
> -------- Original-Nachricht --------
> Betreff: [Lapackpp-devel] Bug?
> Von: Jan Korous <kor...@gm...>
> An: lap...@li...
> Datum: 18.09.2010 18:08
>
>> Hello,
>> I intended to use Lapack++ in my CFD project for diploma thesis. But I
>> found something stange. This simple code crashes, segfault...
>>
>> #include <stdio.h>
>> #include <lapackpp/gmd.h> // LaGenMatDouble
>>
>> using namespace std;
>> int main() {
>>       LaGenMatDouble matrix ( 25440, 25440 );
>>       cout << matrix(0, 8675);
>>       return 0;
>> }
>>
>> I don't know what's going on. I am using version 2.5.3 Are you able to
>> reproduce the bug or is it just me?
>>
>> Thank you for your answer.
>>
>> Sincerely
>> Jan Korous
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> lapackpp-devel mailing list
>> lap...@li...
>> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel
>

Re: [Lapackpp-devel] Bug?

[Dee <de...@de...>]

Hello,

I get this result:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

The problem is in

#5  0x00007ffff75c721e in __cxa_throw () from /usr/lib/libstdc++.so.6
#6  0x00007ffff75c76ad in operator new(unsigned long) () from
/usr/lib/libstdc++.so.6
#7  0x00007ffff75c7769 in operator new[](unsigned long) () from
/usr/lib/libstdc++.so.6
#8  0x00007ffff7bbfa19 in VectorDouble::VectorDouble(unsigned int) ()
from /usr/lib/liblapackpp.so.14
---Type <return> to continue, or q <return> to quit---
#9  0x00007ffff7ba3761 in LaGenMatDouble::LaGenMatDouble(int, int) ()
from /usr/lib/liblapackpp.so.14
#10 0x0000000000400a87 in main () at lap.cpp:9

So I suppose the resulting vector of size 647193600 is too big for the
stack (or heap).

Greetings
Dee


-------- Original-Nachricht --------
Betreff: [Lapackpp-devel] Bug?
Von: Jan Korous <kor...@gm...>
An: lap...@li...
Datum: 18.09.2010 18:08

> Hello,
> I intended to use Lapack++ in my CFD project for diploma thesis. But I
> found something stange. This simple code crashes, segfault...
> 
> #include <stdio.h>
> #include <lapackpp/gmd.h> // LaGenMatDouble
> 
> using namespace std;
> int main() {
>       LaGenMatDouble matrix ( 25440, 25440 );
>       cout << matrix(0, 8675);
>       return 0;
> }
> 
> I don't know what's going on. I am using version 2.5.3 Are you able to
> reproduce the bug or is it just me?
> 
> Thank you for your answer.
> 
> Sincerely
> Jan Korous
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> lapackpp-devel mailing list
> lap...@li...
> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel

[Lapackpp-devel] Bug?

[Jan K. <kor...@gm...>]

Hello,
I intended to use Lapack++ in my CFD project for diploma thesis. But I
found something stange. This simple code crashes, segfault...

#include <stdio.h>
#include <lapackpp/gmd.h> // LaGenMatDouble

using namespace std;
int main() {
      LaGenMatDouble matrix ( 25440, 25440 );
      cout << matrix(0, 8675);
      return 0;
}

I don't know what's going on. I am using version 2.5.3 Are you able to
reproduce the bug or is it just me?

Thank you for your answer.

Sincerely
Jan Korous

[Lapackpp-devel] LAPACK++: Error with ill-conditioned system

[Stefano C. <ste...@an...>]

Hi,

first of all: I have been using Lapack++ over the last two years and,
well, thanks a lot for developing it. It has been of much use in my
research (I'm an OR PhD student).

I am registering an issue when solving an ill-conditioned system Ax = b,
where
A = [ 0.138071  -0.683418  0.169102 ;
-0.333333  -0.471405  0.816497 ;
1  -2.82843  0 ]

and b = [  1 1 1]'.

The solutions I get, with the three LinearSolve functions in Lapack++, are

LaLinearSolve: [1.04761e+15 3.70385e+14 6.41525e+14]
with residuals = [0.0132217 -0.00119019 -0.117126]

LaLULinearSolve: [1.04761e+15 3.70385e+14 6.41525e+14]
with residuals = [0.0132217 -0.00119019 -0.117126]

LaQRLinearSolve: [9.25854e+14 3.27339e+14 5.66968e+14]
with residuals = [-0.0255127 0.099823 0.0626831]

With GNU Octave 3.3.3. I get the solution:
  -2.6147e+06
  -9.2445e+05
  -1.6012e+06
with residuals
   1.00000
   1.00000
   1.00000

I though the underlying FORTRAN LAPACK routines used by Lapack++ and
Octave were the same, though it seems that they are not. Is it possible
that there is some issue in the linear system solving routines?

Can I give you more any more detailed information?

Thanks a lot,
-Stefano

Re: [Lapackpp-devel] Problems with LapackPP 2.5.2/ 2.5.3

[Christian S. <sti...@tu...>]

Hi,

I'm sorry, but I don't work with lapackpp anymore. If you have questions 
concerning this project, please ask on the mailing list lapackpp-
de...@li... (subscription required).

As for code suggestions: Thanks for the proposed include,  I've added those to 
SVN.

If you are interested in working on the code further, I would gladly add you 
as a developer on sourceforge so that you have direct SVN write access.

As for the H_Dot_Prod: There could very well be errors on the x86_64 platform 
for the definitions either of LACOMPLEX *or* in the declaration of lapack's 
implementation function of the dot product: On some platforms, it returned the 
result by-value, whereas on other platforms, it returned the result in one of 
the input arguments, and currently ./configure should check for this during 
configure. This might be wrong on platforms which didn't exist years ago when 
those tests were written, so there might be errors here.

Regards,

Christian


Am Sonntag, 14. März 2010 schrieben Sie:
> Hello,
> 
> My name is Nadav I am a PhD student in Tel Aviv University (E.E
>  department). I have successfully  installed (using make) lapackpp 2.5.2
>  and 2.5.3 on my open suse 11.2 Linux system (see uname below).
> 
> However, using make check revealed two bugs. One was easily solved by
>  inserting
> 
> #include<fstream> inside the following file:
> 
> blaspp/testing/tblasd++.cc
> 
> The second problem was inside the file:
> 
> blaspp/testing/check_blas1pp.cc .
> 
> It failed in line 29 where the routine "Blas_H_Dot_Prod" was unsuccessfully
> checked.
> 
> It looks like something is wronge with the LACOMPLEX definitions.
> 
> I would very much appreciate any kind of help from you.
> 
> Thanks, Nadav
> 
> 
> Linux  2.6.31.12-0.1-default #1 SMP 2010-01-27 08:20:11 +0100 x86_64 x86_64
> x86_64 GNU/Linux
> 
> 
> --
> 
> Open WebMail Project (http://openwebmail.org)
>