thanks for the heads up chris, I wondered if that might be the case.
Maybe a note in the opencolorio readme to temporarily uninstall openimageio if present before building the package would be useful?
regards, Tim

On 20/01/2024 01:31, Christoph Willing wrote:
On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:
since the pybind11 update opencolorio is no longer building for me.
[]

I don't know why it's trying to link to libOpenImageIO files when it is not marked as a dependency (I do have openimageio-2.2.21.0-4 installed)
anyone else seeing this or got a fix?
thanks,Tim

openimageio and opencolorio will each try to link against the other if present. It's an unfortunate "natural" recursive dependency which I try to minimise in the .info files by setting opencolorio as a dependency of openimageio but _not_ setting openimageio as a dependency of opencolorio. This attempted minimisation fails in the case where openimageio is already installed when building opencolorio, which is exactly your situation.

If a clean VM for building is not available, I would recommend that you temporarily remove openimageio, then build opencolorio, then reinstall (or even better: rebuild & install) openimageio.

chris

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to