lapackpp-devel

[Lapackpp-devel] compilation on Mac OS X

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

Hi,
it's me again. i've tried to compile lapackpp on Mac OS X.
There were to minor problems :

_ Test to link a program in FORTRAN in configure script fails : i had to 
set FLIBS to :  FLIBS="-L/sw/lib -lfrtbegin -lg2c -lSystem" before this 
test.

_ For an obscure reason, gfgrc returns a compilation error. It does not 
accept the variable name "_A". I did not waste time in searching a 
magical g++ flag to solve this problem, so i renamed the variable _Algmc 
(it's a LaGenMatComplex).

Now it is ok. I send you this "report" as a piece of feedback. I've only 
tested this solution on one apple G5 with this version of Mac Os : 
powerpc-apple-Darwin 7.8.0 (i think it's Mac Os 10.2).

Best regards,
Jean-Baptiste

Re: [Lapackpp-devel] compilation on Mac OS X

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

Dear Jean-Baptiste,

thank you very much for this feedback. I added the FLIBS to the documentati=
on,=20
and I changed this mysterious _A variable into a different name. An upcomin=
g=20
release 2.1.3 will include these fixes.=20

Thanks again for pointing this out.

Christian Stimming

Am Donnerstag, 10. M=E4rz 2005 11:16 schrieb Jean-Baptiste Charlety:
> Hi,
> it's me again. i've tried to compile lapackpp on Mac OS X.
> There were to minor problems :
>
> _ Test to link a program in FORTRAN in configure script fails : i had to
> set FLIBS to :  FLIBS=3D"-L/sw/lib -lfrtbegin -lg2c -lSystem" before this
> test.
>
> _ For an obscure reason, gfgrc returns a compilation error. It does not
> accept the variable name "_A". I did not waste time in searching a
> magical g++ flag to solve this problem, so i renamed the variable _Algmc
> (it's a LaGenMatComplex).
>
> Now it is ok. I send you this "report" as a piece of feedback. I've only
> tested this solution on one apple G5 with this version of Mac Os :
> powerpc-apple-Darwin 7.8.0 (i think it's Mac Os 10.2).
>
> Best regards,
> Jean-Baptiste
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> lapackpp-devel mailing list
> lap...@li...
> https://lists.sourceforge.net/lists/listinfo/lapackpp-devel

Re: [Lapackpp-devel] compilation on Mac OS X

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

Dear Jean-Baptiste,

Jean-Baptiste Charlety schrieb:
> Dear Christian,
> i have forgotten a step : i had to use the tool libtoolize to copy files 
> like config.guess and config.sub in lapackpp repertory. Maybe those 
> which were supplied in the distribution were too old ?

You mean when you retrieved your sourcecode from CVS, you needed to call 
libtoolize? That's intentional; in fact, exactly for that reason the 
README says that in this case you need to call "make -f Makefile.dist" 
which in turn will call libtoolize. The reason for this is that all 
these files are auto-generated by your installed version of the 
autotools. If they were copied into CVS, you would get conflicts as soon 
as different developers are working with different versions of the 
autotools. And since these are auto-generated anyway, they can be 
generated by each developer individually.

Anyway, this only concerns people who use the source from CVS. All 
others will get a tarball which includes all these necessary files.

Best regards,

Christian