importing pyfftw fails with ImportError/undefined symbol fftwl_plan_with_nthreads

[Ghislain Vaillant]

Forwarded from Debian-Bug#8626036.

The current version of the pyfftw package is currently unusable because of a buggy patch. The latter should be replaced by the patch accompanying this report. Please consider updating the current package deployed in Ubuntu 16.04. Subsequent versions of Ubuntu will be fixed with an upcoming update of the packaging on Debian.

Thanks,
Ghis

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "Detect-fftw-libraries-using-pkgconfig.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Erich E. Hoover (ehoover)]

Can we get this fixed in 16.04? It is really inconvenient to require end-users to install pip and build pyfftw themselves...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Erich E. Hoover (ehoover)]

I made a PPA for this fix ( https://launchpad.net/~sweptlaser/+archive/ubuntu/pyfftw/+packages ), but it would be really nice if this could be incorporated into the official package.

[Ghislain Vaillant (ghisvail)]

Official pyfftw packaging was dropped from Debian, since the latter fails to test on !x86 architectures. I'd be happy to re-introduce this package once this issue is addressed.

There is a bug opened upstream here:

https://github.com/pyFFTW/pyFFTW/issues/128

[Erich E. Hoover (ehoover)]

The package was not dropped from Ubuntu, it just doesn't work (removing the package from the repo would be better than having a completely broken package). I have access to a large number of armhf systems, so it's possible that I can help upstream get their issue sorted out.

[Ghislain Vaillant (ghisvail)]

On Fri, 2017-02-24 at 14:43 +0000, Erich E. Hoover wrote:
> The package was not dropped from Ubuntu, it just doesn't work (removing
> the package from the repo would be better than having a completely
> broken package).

Removal would probably be better and safe, assuming pyfftw has no
rdepends in the archive.

> I have access to a large number of armhf systems, so
> it's possible that I can help upstream get their issue sorted out.

That would be great, although the issue does not only concern arm-based
architectures.