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
pyFFTW import segfaults on armhf #141
Comments
Odds are high that this is an issue merely with my toolchain... close the issue if this discussion is unwelcome. FFTW's test fails:
|
Issue's with FFTW! |
Oh sorry, I totally missed this issue! Interesting to know about the problem, so thanks. |
@hgomersall NP, hope it helps. PyFFTW is great, FFTW just sometimes feels like it's rooted firmly in the past. IE: A release claiming to officially support ARM+NEON that segfaults when compiled on multiple versions of widely-deployed GCC, unless you patch out a feature? sigh Other issue I encountered here was just the under-documented "you must compile fftw by hand three times" which I've seen mentioned in several different places here on GH Issues. |
@itdaniher Yes, I'm acutely aware of that issue. I've been very busy for quite a while. I would genuinely value assistance with any of the issues, but I've no doubt I will eventually reach them! |
libfftw built from http://fftw.org/fftw-3.3.6-pl1.tar.gz the requisite three times, one of which with --enable-neon for simd-accelerated singlefp work.
I think this is an issue with libfftw and (presumably) my GCC version. I'm continuing to explore this - opening issue here as there's a nontrivial amount of discussion about pyfftw on armhf, #128, #127, #70
The text was updated successfully, but these errors were encountered: