On Monday, 25 June 2018 10:27:08 PDT Douglas, William wrote:
Looking at https://github.com/clearlinux/autospec/pull/175
considering how to best integrate this kind of feature. Thiago brought
up the idea of a script that could do mv and could be generic for
different build systems that could live in autospec. I liked that idea
but does anybody have other thoughts or do they think the current
proposed patch is better for our needs?
As you can see from the patch, the way to build a qmake-based package with
AVX2 and have it install in /usr/lib64/haswell is hacky and very ugly. The mv
solution would be neater and would allow me to do the same for plugins too.
Another reason to do that is that many packages hardcode the library path you
passed when configuring --libdir=/usr/lib64/haswell. This may or may not have
side-effects we want. For example, if the software in package foo tried to
find plugins or other architecture-specific files relative to $libdir, it
would fail to find them in /usr/lib64/haswell/foo/bar.so. So letting this
particular software be compiled with --libdir=/usr/lib64 and then move the
library after installation would make it continue working.
The counter-example are self-relocating libraries that read /proc/self/maps to
find out where they are stored in the filesystem. If they are configured with
--libdir=/usr/lib64 but find themselves at /usr/lib64/libfoo.so, they'd be
I think the latter case is very rare and therefore I suggest we start using
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center