Open Arniiiii opened 1 year ago
I guess the reason why is that meson tries to get some info using
flang-new -Wl,-v
, but it should be something likeflang-new -w -v
but i'm not sure. Maybe the problem is somewhere there: https://github.com/mesonbuild/meson/blob/master/mesonbuild/compilers/fortran.py
As discussed in https://github.com/scipy/scipy/issues/18203.
Probably, the reason is that Meson currently doesn't have support for flang-new. Only for https://github.com/flang-compiler/flang
There's still a bug to be fixed here: fortran_std=legacy
isn't handled correctly for classic flang
, and therefore builds that use it break for no reason. It's also not handled correctly for AMD's Fortran compiler (based on Flang), says the bug report at https://github.com/spack/spack/pull/46922.
I think if it's known that a compiler has support for F77 but doesn't accept -std=legacy
, then the right thing to do is to drop the -std
argument completely (optionally emit a warning?).
Describe the bug meson cannot understand supported standards of flang on termux (android)
To Reproduce install termux ( download from github https://github.com/termux/termux-app/releases ) then in termux:
i got a lot of stuff in console and then there was path to such log: https://bpa.st/SWLEC
Expected behavior I guess it should stop not at point
I guess the reason why is that meson tries to get some info using
flang-new -Wl,-v
, but it should be something likeflang-new -w -v
but i'm not sure. I guess so because:Maybe the problem is somewhere there: https://github.com/mesonbuild/meson/blob/master/mesonbuild/compilers/fortran.py
system parameters termux, android, a samsung phone meson -- git version and all below i guess ( tried with another previous... ) ninja ( in the case it doesn't matter, but 1.11.1 )