Re: Problems with CLAPACK SVD routines on OS X

mecej4 wrote:
H.S. wrote:
Robert V. wrote:
Hello,

<<--C U T-->>
#include <vecLib/vecLib.h>

I am not familiar with this header file. What does it do and why do you
need it?

So that he does not generate all the error messages below! Obviously,

I see that one of the errors is due to the absence of this file. How is
it obvious that the others are due to this as well?

Note that the OP is new to C++ source code and is using examples to try
out the library. He may have got the header line from some example and
just never thought about it in his own. This happens. I wanted to make
sure if this was the case.

->HS




the header file contains needed definitions, in the absence of which
compilation will not be successful.

-- mecej4

I wanted to run this code of yours (I have lapack libraries installed on
my Linux system) but I do not have a data file that you are trying to
read. But I couldn't get the program compiled ....


g++ svd_test.cpp -I/usr/local/include -framework vecLib -o svd

... If I try to compile your program, I get (after excluding fstream and
sstream headers):

$> g++ testsvn.cc ~/lib/lapack_LINUX.a -I~/include/ -o testsvd
testsvn.cc:1:27: error: vecLib/vecLib.h: No such file or directory
testsvn.cc: In function ‘int main(int, char**)’:
testsvn.cc:27: error: variable ‘std::ifstream infile’ has initializer
but incomplete type
testsvn.cc:46: error: variable ‘std::istringstream s’ has initializer
but incomplete type
testsvn.cc:85: error: variable ‘std::istringstream s’ has initializer
but incomplete type
testsvn.cc:91: error: statement cannot resolve address of overloaded
function
testsvn.cc:122: error: ‘dgesvd_’ was not declared in this scope


<<--C U T-->>
.

Relevant Pages

  • Re: Another spinoza challenge
    ... implementation-defined variable in a header would be valid. ... An implementation could define behaviour for this post making it valid C, so by your definition EVERY possible file is valid C since some implementation could define behaviour for it. ... It should be pretty clear that it is, reserved for the implementation because of the leading _, but it is a valid identifier. ... Yes, which make it not unambiguously valid, since it might not be valid (as in an attempt to use it as an identify might cause compilation to abort with an error). ...
    (comp.lang.c)
  • Re: A question about ifndef
    ... >> Ben Pfaff wrote: ... >>>It's not just for compilation performance. ... >>>probably omit them in my header files, ... > struct fred {int i;}; ...
    (comp.lang.c)
  • Re: matrices
    ... There is no standard header. ... Doing it indirectly does NOT help improve compilation speed ... These two statements above are very strange. ... addition operator shouldn't be telling everybody it's doing its job. ...
    (comp.lang.cpp)
  • Re: What is LISP good for, that is harder in other languages?
    ... |> A much bigger problem is that you need to construct ... | compilation unit requires the compiler to start from a completely blank ... This also used to be a problem with TOPS-10 Monitor builds. ... small sources files each with *dozens* of includes of header ...
    (comp.lang.lisp)
  • Re: Best Practices: #include
    ... It does not require that the header file be included in every file; ... If the header file has been included once, in a given compilation, any subsequent ... the file not be included by #pragma once until it has been included one time, ... allows the header to be read where it's contents are unknown" is also content-free. ...
    (microsoft.public.vc.mfc)
Loading