In this case it *is* just a standard "hidden" dependency - if it's present
at configure time then cython is used for the build. It just needs either
enabling properly with whatever *_DEPENDS lines are appropriate, or
disabling either via flags/environment or patches.
Generally if it's just a build conflict then it should just be fixed.
--
Sent from a phone, apologies for poor formatting.
On 12 April 2019 18:51:48 Kurt Mosiejczuk <[email protected]> wrote:
On Fri, Apr 12, 2019 at 03:59:45PM +0100, Stuart Henderson wrote:
On 2019/04/12 16:14, Christian Weisgerber wrote:
math/py-pandas,python3 failed to build in my latest amd64 bulk build.
Any idea what happened there?
Hidden optional dep. py3-Cython was present when configure started
running. but then got junked.
I see this sort of thing come up more than once where something isn't a
dependency per se, but if it happens to be there, it causes chaos.
It's not really a conflict, would the idea of a mechanism to document a
"build conflict" be useful for ports building? Something that might allow
making sure such a package is not installed when building?
--Kurt
