py32-numpy (but other version also?) does not link against libgomp when needed

[Veence (Vincent)]

It seems when using an OpenMP enabled compiler, macports-gcc-4.7 for instance, the lapack_lite.so module of numpy (name given from memory) does not link against libgomp, thereby creating an unknown symbol error at runtime. I saw this on an old G4 box (MacOS 10.4), it would have to be confirmed for other combinations of MacOS / Python.

Fix is to add ${prefix}/lib/gccXX/libgomp.dylib in the extra_link_args line of patchfile ‘patch-numpy_linalg_setup.py.diff’

[lpsinger (Leo Singer)]

Better than explicitly linking against libgomp is to to pass -fopenmp to both the compiler and the linker.

[Veence (Vincent)]

Yes, you’re right, I’d forgotten this flag. Thanks for pointing it out.

[skymoo (Adam Mercer)]

Replying to aronnax@…:

Better than explicitly linking against libgomp is to to pass -fopenmp to both the compiler and the linker.

Leo: feel free to make the required changes as you're more familiar with OpenMP.

[lpsinger (Leo Singer)]

Whichever source files use OpenMP pragmas would have to be compiled with -fopenmp too. Which source files in Numpy use OpenMP?

[Veence (Vincent)]

The error was solely reported in the lapack_lite.so module. I think it is tied to gfortran, but I can’t be fully positive. What is certain is that, after adding the library in the patch file, as I wrote before, I built a numpy passing all self-tests.

[cooljeanius (Eric Gallager)]

Cc Me!

[petrrr]

Cc Me!

[petrrr]

I assign (CC) this to the maintainer to check if this is still relevant. py32 subport is gone, but might be relevant to other subports as well.

[mf2k (Frank Schima)]

dh has retired. See #51239.

[Veence (Vincent)]

• Not relevant anymore -