usr/lib/python2.3/site-packages/_lcms.so usr/lib64/liblcms.so.1.0.13 making executable: /usr/lib64/liblcms.so.1.0.13 !!! ERROR: media-libs/lcms-1.13-r1 failed. !!! Function dyn_install, Line 1110, Exitcode 0 !!! File /tmp/portage/lcms-1.13-r1/image///usr/lib/python2.3/site-packages/_lcms.so matches a file type that is not allowed in /usr/lib Reproducible: Always Steps to Reproduce: FEATURES=multilib-strict emerge lcms Actual Results: Failure due to multilib-strict error above Expected Results: Obeyed the $LIBDIR stuff, successful merge. emerge info to be attached
Created attachment 57243 [details] emerge info output
Python modules inherit the site-packages path from the installed instance of python. Please re-emerge python (to be sure that that is fully multilib-strict) and then try to emerge lcms. If you still have the error then pls state which version of python you're using.
Thanks for the explanation. Remerged python, then lcms, and had no problems this time around. Note that the issue will ultimately still need to be dealt with, probably as a step in the upgrade process, when we do get rid of the lib/lib64 symlink, which is after all what the whole multilib-strict thing is supposed to be testing. If that's already on the list, the bug can be resolved, as it now works here. However, I'll leave the resolution up to "y'all", in case y'all want to keep the bug open until that step is added to the 2005.1 (or whatever) upgrade guide. BTW, where is this path located? I'd like to actually take a look-see. (One of my near-term projects is Learning Python, the book as well as the task, but I haven't but read the intro at this point, so...)
OK, resolving this as fixed then. FYI the python extension module directory is defined at python compile time and can be extracted by running: # python -c "from distutils import sysconfig; print sysconfig.get_python_lib(1,0,prefix='/usr')"
