Hi, Ninja should either support Fortran compiler (e.g. add this functionality) or should not be used for packages compiling Fortran code. There are multiple bugs about this already.
*** Bug 558632 has been marked as a duplicate of this bug. ***
*** Bug 558592 has been marked as a duplicate of this bug. ***
*** Bug 558244 has been marked as a duplicate of this bug. ***
ninja has never claimed to support fortran. If the feature is desired, it needs to be requested upstream. People should not be setting CMAKE_MAKEFILE_GENERATOR=ninja globally if they are going to be building fortran packages.
(In reply to Mike Gilbert from comment #4) > ninja has never claimed to support fortran. If the feature is desired, it > needs to be requested upstream. I wasn't aware of this, sry. > People should not be setting CMAKE_MAKEFILE_GENERATOR=ninja globally if they > are going to be building fortran packages.
Actually, ninja has any built-in support for compiling any language; that has to be defined in build rules by the program that generates the ninja files. I suspect the cmake generator for ninja simply does not generate valid ninja files for compiling fortran. Re-opening.
(In reply to Mike Gilbert from comment #6) > Re-opening. Do you accept furthermore bug reports of this kind (with blocker to "ninja-porting") or will those be declined ?
(In reply to Toralf Förster from comment #7) > Do you accept furthermore bug reports of this kind (with blocker to > "ninja-porting") or will those be declined ? I don't think it makes sense to file bugs for individual fortran packages at this point. The fix is likely to be in cmake or the eclass, and not in the individual packages.
From cmake-3.7.0_rc1 (in tree without keywords currently) changelog: * The "Ninja" generator learned to conditionally support Fortran when using a "ninja" tool that has the necessary features. See generator documentation for details.
(In reply to Michael Palimaka (kensington) from comment #9) > * The "Ninja" generator learned to conditionally support Fortran > when using a "ninja" tool that has the necessary features. See > generator documentation for details. I think that Gentoo's ninja package does not satisfy this. We provide the a package based on https://github.com/ninja-build/ninja, whereas cmake wants a ninja package with several changes that have not yet been merged: https://github.com/Kitware/ninja.
We'll get ninja/fortran support if and when it lands in ninja upstream, and we don't support officially using ninja globally.
FYI from the cmake-3.11 release notes: * The Makefile Generators and the "Ninja" generator learned to add compiler launcher tools along with the compiler for the "Fortran" language ("C", "CXX", and "CUDA" were supported previously). See the "CMAKE_<LANG>_COMPILER_LAUNCHER" variable and "<LANG>_COMPILER_LAUNCHER" target property for details.
Sounds like we can get back to the business. I think the best way forward would be to add a >= dep to the eclass when three new version is in and stable, and then start removing generator overrides.
s/three/the/
Can this be closed?