When =dev-lang/ekopath-5.0.1_pre20131115 is installed and then trying to build cmake, it result to many sandbox violation. -- <<< Gentoo configuration >>> Build type Gentoo Install path /usr Compiler flags: C -march=native -O2 -pipe -fomit-frame-pointer C++ -march=native -O2 -pipe -fomit-frame-pointer Linker flags: Executable -Wl,-O1 -Wl,--as-needed Module -Wl,-O1 -Wl,--as-needed Shared -Wl,-O1 -Wl,--as-needed -- Configuring done -- Generating done -- Build files have been written to: /var/tmp/portage/dev-util/cmake-2.8.12.2-r1/work/cmake-2.8.12.2_build >>> Source configured. * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-24945.log" * Full log attached (portage and sandbox), and emerge --info Reproducible: Always
Created attachment 378332 [details] build.log
Created attachment 378334 [details] sandbox.log
Created attachment 378336 [details] emerge --info
Something similar happens if dev-lang/ifc is installed.
ekopath is fixed not to break sandbox. Now, what remains is CMake trying hard to find a random Fortran compiler.
(In reply to Michał Górny from comment #5) > ekopath is fixed not to break sandbox. Now, what remains is CMake trying > hard to find a random Fortran compiler. Please elaborate. That's not a particularly useful piece of information.
-- Looking for a Fortran compiler -- Looking for a Fortran compiler - /opt/ekopath/bin/pathf95 I'm not convinced that Gentoo packages should try to use non-GNU compilers implicitly, and what are the implications of that.
AFAIK it's only checking out the environment as part of build. Anything actually using fortran and cmake-utils.eclass gets tc-getFC automatically.
