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
>