lapackpp-devel

[Lapackpp-devel] linker error with lapackpp-2.1.0

[Jean-Baptiste C. <Jea...@in...>]

hi,
i'm trying to link my software with the last version of Lapack++ (2.1.0) 
and i get a linker error that i did not have with previous version (2.0.3) :

..../lapackpp-2.1.1/include/lapackpp/genmd.h:88: multiple definition of 
`LaRandUniform(LaGenMatComplex&, double, double)'

If i comment out this function in genmd.h, the linker error disappears. 
Have you an idea to solve this problem more properly ?

cheers,
JB Charlety

Re: [Lapackpp-devel] linker error with lapackpp-2.1.0

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

Hi,

good to hear that other people are using our software :-)

I didn't see any of these linker errors so far, so your environment is 
probably different than mine. What compiler is this? And how do you 
include your Lapack++ headers?

I'd guess you are using
#include <lapack++.h>
or something comparable to this, and yes, there were some changes in the 
inclusion order inside that header file. This might result in the fact 
that the _LA_GEN_MAT_COMPLEX_H_ macro is now defined, which will make 
this function visible, whereas in previous versions it might have been 
invisible.

Jean-Baptiste Charlety schrieb:
> ..../lapackpp-2.1.1/include/lapackpp/genmd.h:88: multiple definition of 
> `LaRandUniform(LaGenMatComplex&, double, double)'
> 
> If i comment out this function in genmd.h, the linker error disappears. 
> Have you an idea to solve this problem more properly ?

I don't understand why the function definitions have been written in the 
header file in the first place. I'd have expected them to be written in 
the cpp file, but that's how they came from lapack++ version 1.1. 
Nevertheless the linker error should also disappear if you make the 
function declaration "inline", i.e. you write

inline LaGenMatComplex& LaRandUniform(LaGenMatComplex &A, double low, 
double high)
{ // ....

Does this fix the problem, too? If it does, I'll quickly make a new 
release with this bugfix.

Christian

Re: [Lapackpp-devel] linker error with lapackpp-2.1.0

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

Hi Jean-Baptiste,

thanks for this feedback. I changed the header file and made a new 
release 2.1.2 which includes this change.

  http://sourceforge.net/project/showfiles.php?group_id=99696

If you encounter any further problems, do not hesitate to contact me again.

Best regards,

Christian


Jean-Baptiste Charlety schrieb:
> Hi !
> 
> Christian Stimming wrote:
> 
>> Hi,
>>
>> good to hear that other people are using our software :-)
> 
> 
> We are currently using Lapack++ library in first SICONOS project 
> software prototype. Lapack++ is interesting for us because we need C++ 
> classes to represent matrices and vectors of floating numbers, which are 
> usable with FORTRAN routines (column oriented data storage) .In fact, we 
> were about to leave out Lapack++ in July 2004, because version 1.1 was 
> no more in development (and was unsatisfactory).
> We discovered last summer that you have decided to continue the 
> development of this library thanks to Google, and that's a good news !
> 
>> I didn't see any of these linker errors so far, so your environment is 
>> probably different than mine. What compiler is this? 
> 
> 
> My compiler is : g++ (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) (my OS 
> : Linux Fedora core 2)
> 
>> And how do you include your Lapack++ headers?> I'd guess you are using
>> #include <lapack++.h>
>> or something comparable to this, and yes, there were some changes in 
>> the inclusion order inside that header file. This might result in the 
>> fact that the _LA_GEN_MAT_COMPLEX_H_ macro is now defined, which will 
>> make this function visible, whereas in previous versions it might have 
>> been invisible.
> 
> 
> You are right, I include my lapack++ headers like that.
> 
>> I don't understand why the function definitions have been written in 
>> the header file in the first place. I'd have expected them to be 
>> written in the cpp file, but that's how they came from lapack++ 
>> version 1.1. 
> 
> 
> I agree with you, this is pretty strange, and must be awful to debug !
> 
>> Nevertheless the linker error should also disappear if you make the 
>> function declaration "inline", i.e. you write
>>
>> inline LaGenMatComplex& LaRandUniform(LaGenMatComplex &A, double low, 
>> double high)
>> { // ....
>>
>> Does this fix the problem, too? 
> 
> 
> Yes ! It's ok with the addition of "inline", thank you ! I did not get 
> this idea yesterday.
> 
>> If it does, I'll quickly make a new release with this bugfix.
>>
>> Christian
> 
> 
> Best regards,
> Jean-Baptiste
>