[Bug 211768] [NEW PORT] net/py-mpi4py-{openmpi,mpich2}: MPI for Python
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Aug 12 14:10:04 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211768
--- Comment #13 from Michael Danilov <mike.d.ft402 at gmail.com> ---
Evening, Kubilay,
I believe the FATALs in the slave port, as far as my understanding goes,
originate from portlint confusing somethinig, because similar ones appear in
"www/vimb-gtk3" that was accepted for commit some time ago.
Would CONFLICTS_INSTALL be better than CONFLICTS?
According to README.rst, the package needs cython -- in fact, it looks for MPI
header files and compiles something. I have tried testing without, but
configure fails.
Additionally, there is no generic MPI .mk like in NetBSD so far (perhaps it
still needs to pick MPI implementation globally?) and OpenMPI and MPICH2
install files in different locations (/usr/local/mpi/openmpi vs. /usr/local).
With options it will be impossible to have packages using all MPI
implementations in the same binary repo, and should the user need different
MPI, they are left with ports?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-python
mailing list