-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FFTW3 file referenced in a FFTW2 compilation #109
Comments
Oh dear! It's a long time since this has been tested. Is there a particular reason you want to do this? |
The GADGET3 version I'm using only supports FFTW2 and I wanted to keep everything in my pipeline within the same environment. It's not a big deal, I can change to FFTW3 when generating the ICs, I was just wondering if it was an issue on my end. |
Not likely to be a problem on your end. The code isn’t regularly tested against FFTW2 so probably at some point an error has slipped in where it still tries to include FFTW3 headers. You could try editing out those FFTW3 headers manually to see whether it fixes it. We can add FFTW2 to the CI matrix if this is important, it’s just an oversight that I think we had all forgotten about it… |
No worries!
but it wasn't as easy as that 😄 For the time being, I can stick to FTTW3 and focus on other issues. If it's OK with you, maybe we keep this issue open so the rest of the users are aware of it? |
Looking at this, I think it's been too long since we used FFTW2 and it would be significant work to reintroduce and test it. Thanks for spotting it, though, I'll update the documentation to remove any reference to being able to work with FFTW2. |
Hi,
I want to compile genetIC with FFTW2 support. Following the documentation, I commented the FFTW3 flags and instead turned on the FFTW2 ones:
but at compilation time I get
It seems that fourier.hpp, which is included in main.cpp through ic.hpp, calls fftw3.h even with the FFTW2 flags on. Is there something else I am not configuring properly?
The text was updated successfully, but these errors were encountered: