All dev-libs/boost ebuilds hardcode the path to the directory where the Intel compiler is installed. When using the 8.1 version this breaks 8.0 is hardcoded. Reproducible: Always Steps to Reproduce: 1. Emerge a newer icc version then needed for the boost ebuild (at least one minor version higher e.g. 8.1 instead of 8.0) 2. Emerge dev-libs/boost with the icc USE flag on 3. The build process fails The sollution is simple: (From the icc manpage) ENVIRONMENT VARIABLES You can customize your environment by setting the following environment variables. You can specify paths where the compiler can search for special files such as libraries and include files. ... IA32ROOT (i32 only) Points to the directory containing the bin, lib, include and substitute header directories. IA64ROOT (i64 only) Points to the directory containing the bin, lib, include and substitute header directories. So the ebuild can look for these environment variables to locate the path to icc files.
Created attachment 65091 [details] Proposed ebuild that detects the Intel compiler path boost-1.32.0-r5.ebuild uses the IA32ROOT or IA64ROOT environment variable to detect the location of the Intel compiler. This ebuild works for me with IA32ROOT, but IA64ROOT is not tested, nor is the situation when both variables are empty.
please test the masked 1.33.0-r1 ebuild if this works for you, i don't have the ability to test icc here thanks for the work too
please test 1.33.0-r1 one hour from this message
thank you for your work, unfortunately i decided to deprecate icc support alltogether due to lack of support for icc in gentoo
