Re: How to deal with clapack - is it (or a replacement) packaged

[Andreas Tille <andreas@an3as.eu>]

Hi again,

On Thu, Apr 21, 2016 at 09:58:13AM +0100, Ghislain Vaillant wrote:
> >I somehow brute forced a patch
> >
> >--- a/include/external_libs.h
> >+++ b/include/external_libs.h
> >@@ -39,8 +39,8 @@
> >  #else
> >
> >  #ifndef SKIP_LAPACK
> >-#include <f2c.h>
> >-#include <clapack.h>
> >+/* #include <f2c.h> */
> >+#include <lapacke.h>
> >  #define LAPACK_INT integer
> >  #define LAPACK_DOUBLE doublereal
> >  #endif  /*ifndef SKIP_LAPACK */
> 
> integer and doublereal are defined in f2c/clapack, which your patch actually
> replace with lapacke hence the unknown type.

Could you provide an example patch to get me starting with the port or
help estimating the effort to port from clapack to lapacke.
 
> See this blog post for a good reasoning:
> http://nicolas.limare.net/pro/notes/2014/10/31_cblas_clapack_lapacke/

While this sounds convincing I have spotted some other potential
packaging target using clapack and may be the porting work is more
effort than just another package?

Kind regards

     Andreas.

-- 
http://fam-tille.de