* Donnie Berkholz [2007-08-19 05:27]: > On 22:53 Sat 18 Aug , Adam Piątyszek wrote: >> The problem is that now the IT++ ebuild can not automatically configure >> the use of FFT native interfaces from MKL and ACML, when they are used >> as BLAS and LAPACK external libs. It should work as follows: If one have >> ACML or MKL installed, there is no need to install FFTW additionally. To >> configure these specific FFT interfaces, the existence of <mkl_dfti.h> >> and <acml.h> headers is verified, but of course it does not work, >> because these headers are installed in vendor specific directories. >> >> I discussed this issue with Markus some time ago and I proposed to >> append unconditionally "-I/path/to/acml.h -I/path/to/mkl_dfti.h" to >> CPPFLAGS and pass it to the configure command. But this solution is a >> bit "dirty". Now I wonder how to make this work properly in the IT++ >> ebuilds. Maybe you have some ideas for this? > > Yeah, a good approach would use something like blas-config to get > include paths. Do we need an fft-config?
Maybe... But, the other problem is that these FFT implementations that IT++ can use (FFTW, MKL, ACML) have completely different interfaces. So it is not the same situation as for various BLAS and LAPACK implementation... /Adam -- .:. Adam Piatyszek - "ediap" .:. JID: ediap(at)jabber.org .:. .:. ediap(at)users.sourceforge.net .:. PGP key ID: 0x1F115CCB .:.
smime.p7s
Description: S/MIME Cryptographic Signature
