Looking at the ci-vfxall image, it seems that most of the resulting DSOs end up in /usr/local/lib
but a few end up in /usr/local/lib64 (OpenGL, OIIO, Ptext, OSL). On CentOS 7 systems:
32 bit DSOs: /lib -> /usr/lib
64 bit DSOs: /lib64 -> /usr/lib64
Since these containers are 64 bit only, would it make sense to have all DSOs land in /usr/local/lib64 ? Could always have a backwards compatibility link from /usr/local/lib to /usr/local/lib64
On the other hand systemd defines /lib64 as a "backwards compatibility symlink":
https://www.freedesktop.org/software/systemd/man/file-hierarchy.html#Compatibility%20Symlinks
so it's unclear what's the correct approach, but since for now these containers are somewhat CentOS 7 centric, I would suggest following the lead of CentOS 7, and having all DSOs land in /usr/local/lib64
Looking at the ci-vfxall image, it seems that most of the resulting DSOs end up in /usr/local/lib
but a few end up in /usr/local/lib64 (OpenGL, OIIO, Ptext, OSL). On CentOS 7 systems:
32 bit DSOs: /lib -> /usr/lib
64 bit DSOs: /lib64 -> /usr/lib64
Since these containers are 64 bit only, would it make sense to have all DSOs land in /usr/local/lib64 ? Could always have a backwards compatibility link from /usr/local/lib to /usr/local/lib64
On the other hand systemd defines /lib64 as a "backwards compatibility symlink":
https://www.freedesktop.org/software/systemd/man/file-hierarchy.html#Compatibility%20Symlinks
so it's unclear what's the correct approach, but since for now these containers are somewhat CentOS 7 centric, I would suggest following the lead of CentOS 7, and having all DSOs land in /usr/local/lib64