opencv @2.4.2 +universal configure failure: command execution failed

[lucasvickers@…]

Problem appears to be

-- Could NOT find PythonLibs: Found unsuitable version "2.7.2", but required is at least "2.7.3"

• I have confirmed that Python 2.7.3 is installed multiple times.
• I force uninstalled python, confirmed file '/opt/local/lib/libpython2.7.dylib' was non existant, then installed python 2.7.3 +universal
• I also tried allowing opencv port to control the installation of python 2.7.3.

In every instance opencv port claims the python libs are 2.7.2. I believe this is the point of failure.

[lucasvickers@…]

output from opencv build

[lucasvickers@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I can confirm that opencv +universal does not complete the configure phase on my Lion machine either. However I don't think it has anything to do with python; those python failure messages also appear when you try to install opencv without the universal variant, but that still succeeds.

[lucasvickers@…]

You are correct I was able to compile without the +universal
Does main.log give you any further details?

thanks

[BasicBaer (Hendrik T. Voelker)]

Cc Me!

[lucasvickers@…]

Any rough eta on how long this may take or general turn around time on tickets?
Trying to decide how much effort I should put into compiling elsewhere.

Thanks

[pjue2009@…]

Cc Me!

[BasicBaer (Hendrik T. Voelker)]

It seems that the problem are not the Python libs. The message is just misleading, as the later following CMake code will pick up the correct library.

The problem is that +universal will cause the removal of one include file from the main CMakeLists.txt file which contains a macro that is required later on. While the compile will fail when the include file cmake/OpenCVPCHSupport.cmake is used as is, as it enables PCH, the simple solution is to add a line containing

SET(PCHSupport_FOUND FALSE)

directly after the include. I have attached the new diff file that replaces the old one and does as described above.

[BasicBaer (Hendrik T. Voelker)]

updates patch file

[ryandesign (Ryan Carsten Schmidt)]

Replying to basicbaer@…:

the simple solution is to add a line containing

SET(PCHSupport_FOUND FALSE)

directly after the include

I don't really understand the problem or the proposed solution so I'm a little uncomfortable committing it. I'd feel better if you could show me a statement from the developers of OpenCV stating that this is the correct solution. Or point me to where they've already committed this fix to their repository. If they haven't done that yet, then could you please first work with the developers of OpenCV to get this or some other solution accepted and committed to their repository? Then we can apply the same fix in MacPorts, until they release a new version of OpenCV.

[BasicBaer (Hendrik T. Voelker)]

Replying to ryandesign@…:

I don't really understand the problem or the proposed solution so I'm a little uncomfortable committing it.

I don't understand either why the Universal variant cannot be build with PCH support.

I'd feel better if you could show me a statement from the developers of OpenCV

My patch has nothing to do with the OpenCV developers. I was just replacing the patch file ports/graphics/opencv/files/patch-pch-CMakeLists.txt.diff that is already part of the port. So I fixed the port, not OpenCV.

If they haven't done that yet, then could you please first work with the developers of OpenCV

Honestly I don't feel that as my responsibility as I am not the maintainer of this port.

For me the fix works and I can live with a few port files maintained by myself locally ...

[ryandesign (Ryan Carsten Schmidt)]

Replying to basicbaer@…:

If they haven't done that yet, then could you please first work with the developers of OpenCV

Honestly I don't feel that as my responsibility as I am not the maintainer of this port.

Well clearly nobody has felt it is their responsibility, since nobody has agreed to be this port's maintainer. :)

[mkae (Marko Käning)]

Shouldn't this be closed as wontfix as opencv has advanced in the meantime big time?

[mascguy (Christopher Nielsen)]

Given that we don't support opencv 2.x, can this be closed?

[mascguy (Christopher Nielsen)]

This ticket is no longer relevant, as we don't have an OpenCV 2 port. Can someone close?