Hi,
Sorry I was slow, but I have been working in the yard over the weekend.
I think I found their conftest.c:
#include <fftw3.h>
int
main ()
{
fftw_plan *plan;
fftw_complex *a1, *a2;
fftw_execute_dft(plan, a1, a2);
;
return 0;
}
I renamed the file a little and get errors related to their code. I did notice they put their directory in quotes. I do not think that matters because there is only one, but let me check. Nope, same result as below.
$ mpicc -c -O2 -fPIC -fno-omit-frame-pointer -fopenmp -g -mtune=native -fpermissive -I/opt/cray/pe/fftw/
3.3.10.10/x86_rome/include -o rayfftw.test fftw.test.c
fftw.test.c: In function ‘main’:
fftw.test.c:9:26: warning: passing argument 1 of ‘fftw_execute_dft’ from incompatible pointer type [-Wincompatible-pointer-types]
9 | fftw_execute_dft(plan, a1, a2);
| ^~~~
| |
| struct fftw_plan_s **
In file included from fftw.test.c:1:
/opt/cray/pe/fftw/
3.3.10.10/x86_rome/include/fftw3.h:196:41: note: expected ‘fftw_plan’ {aka ‘struct fftw_plan_s * const’} but argument is of type ‘struct fftw_plan_s **’
196 | FFTW_CDECL X(execute_dft)(const X(plan) p, C *in, C *out); \
| ~~~~~~~~~~~~~~^
/opt/cray/pe/fftw/
3.3.10.10/x86_rome/include/fftw3.h:465:1: note: in expansion of macro ‘FFTW_DEFINE_API’
465 | FFTW_DEFINE_API(FFTW_MANGLE_DOUBLE, double, fftw_complex)
| ^~~~~~~~~~~~~~~
gcc: warning: -I/opt/cray/pe/fftw/
3.3.10.10/x86_rome/include: linker input file unused because linking not done
gcc: error: -I/opt/cray/pe/fftw/
3.3.10.10/x86_rome/include: linker input file not found: No such file or directory
Ray again
Sent: Saturday, September 13, 2025 5:47 AM
To: cp2k
Subject: Re: [External] [CP2K:21833] Re: Unusable FFTW?
To view this discussion visit
https://groups.google.com/d/msgid/cp2k/a5842ef5-55b3-4765-8ab3-b461b9c357f4n%40googlegroups.com<
https://groups.google.com/d/msgid/cp2k/a5842ef5-55b3-4765-8ab3-b461b9c357f4n%40googlegroups.com?utm_medium=email&utm_source=footer>.