Date: Fri, 12 Aug 2016 14:10:04 +0000
From: bugzilla-noreply@freebsd.org
To: python@FreeBSD.org
Subject: [Bug 211768] [NEW PORT] net/py-mpi4py-{openmpi,mpich2}: MPI for Python
Message-ID: <bug-211768-21822-aW2f4uwAnt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211768-21822@https.bugs.freebsd.org/bugzilla/>
References: <bug-211768-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211768 --- Comment #13 from Michael Danilov <mike.d.ft402@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? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211768-21822-aW2f4uwAnt>