Il 13/09/18 20:55, Andreas Sturmlechner ha scritto: > On Donnerstag, 13. September 2018 16:25:13 CEST Mike Gilbert wrote: >> This may effect your plans to enable ninja by default, since it will >> break any fortran package. > Not much concerned about that; backend default can be overridden by package, > should its maintainer find out it breaks by EAPI-7 bump. > > FYI there was a similar discussion some time ago, since than ninja has been the default backend for cmake (desktop system 2k packages), in this time the following packages had (or still have) problems:
# cmake cannot use ninja if it's not installed... dev-cpp/gtest cmake-make dev-util/ninja cmake-make net-analyzer/icinga2 cmake-make media-gfx/gmic cmake-make # ninja: error: 'vendor/scrypt/src/scrypt_original-build/libscrypt_sse2.a', needed by 'src/cryfs-cli/cryfs', missing and no known rule to make it sys-fs/cryfs cmake-make # Fortran not supported sci-libs/blas-reference cmake-make sci-libs/exodusii cmake-make sci-libs/lapack-reference cmake-make # error dev-libs/appstream cmake-make kde-plasma/kinfocenter cmake-make app-doc/doxygen cmake-make net-irc/quassel cmake-make kde-apps/libksieve cmake-make
