You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenImageIO's oiiotool builds and links against LibRaw: since the base image for the ASWF containers is nvidia/cudalgl:${ASWF_CUDA_VERSION}-devel-centos7 that brings a recent version of CentOS 7, in the build I'm looking at CentOS 7.8 which installs LibRaw-0.19.4-1.el7.x86_64.rpm
Thus /usr/local/bin/oiiotool has an explicit dependency on a system installed libraw 0.19 DSO:
Unfortunately earlier, still fairly widely used versions of CentOS (for instance CentOS 7.6) has an earlier libraw version, LibRaw-0.14.8-5.el7.20120830git98d925.x86_64.rpm which installs an earlier versioned libraw_r.so.5:
In the spirit of having ASWF container builds depend as little as possible on "system installed" components (especially for libraries which are particularly relevant to ASWF projects such as libraw), would it make sense to add libraw as an explicit build instead of depending on the system installed version?
The text was updated successfully, but these errors were encountered:
OpenImageIO's oiiotool builds and links against LibRaw: since the base image for the ASWF containers is nvidia/cudalgl:${ASWF_CUDA_VERSION}-devel-centos7 that brings a recent version of CentOS 7, in the build I'm looking at CentOS 7.8 which installs
LibRaw-0.19.4-1.el7.x86_64.rpm
Thus
/usr/local/bin/oiiotool
has an explicit dependency on a system installed libraw 0.19 DSO:Unfortunately earlier, still fairly widely used versions of CentOS (for instance CentOS 7.6) has an earlier libraw version,
LibRaw-0.14.8-5.el7.20120830git98d925.x86_64.rpm
which installs an earlier versioned libraw_r.so.5:/lib64/libraw_r.so.5 -> libraw_r.so.5.0.0 /lib64/libraw_r.so.5.0.0
In the spirit of having ASWF container builds depend as little as possible on "system installed" components (especially for libraries which are particularly relevant to ASWF projects such as libraw), would it make sense to add libraw as an explicit build instead of depending on the system installed version?
The text was updated successfully, but these errors were encountered: