Open barracuda156 opened 1 year ago
this issue seems to be more related to LFortran than stdlib. @certik are you aware of such issue with LFortran?
I've noticed this as well, that cmake picks lfortran over gfortran, I think it shouldn't do that. The LFortran bug here is that it can't compile stdlib yet. The CMake bug is that it can't call lfortran properly in all cases yet, that's something we need to fix in cmake itself.
Description
I was writing a portfile for
stdlib
anew, since being on a different machine, and did not specifygfortran
; CMake build script opportunistically pickedlfortran
(which is fine after all), but decided it is broken because of unexpected flags :)While I did not use
lfortran
for real-life tasks yet, it passes its own tests fine, so definitely not broken.Expected Behaviour
Perhaps build system should be aware of 32-bit platforms.
Version of stdlib
Github
Platform and Architecture
macOS 10.6 ppc
Additional Information
gcc 12.2.0