You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was originally created at: 2008-01-28 00:30:48.
This issue was reported by: cournape.
cournape said at 2008-01-28 00:30:48
mingw fortran compilers do not work with scons out of the box. As such, fortran tools are not initialized, which give non obvious errors like do not know hot to build from a source with suffix .f
Adding support for g77 should be trivial (all the work is done in mingw tool). gfortran is a bit more difficult, because it installs itself in a different directory (c:\program files\gfortran), so I am not sure how to find this automatically.
gregnoel said at 2008-04-14 12:36:24
Bug party triage. Possible toolchain, possible detect().
garyo said at 2008-10-29 18:48:36
I "researched" this but I don't have mingw or gfortran so I didn't do much other than think about it. I think David should come up with a patch if possible. I recommend letting him decide on the schedule, but 2.x/p3 seems OK to me. If he doesn't have mingw Fortran, hand off to someone who does.
Setting target back to unspecified for re-triage.
gregnoel said at 2008-11-08 18:32:12
If mingw is correctly detected as not present, this is the same problem as when a C compiler (or SWIG or ...) is not present: files with that suffix are not handled correctly. In this case, it sounds like the compiler is not installed in the PATH, so it wouldn't work from the command line, either. If it is installed in the PATH, but not in SCons' PATH, then I'd like to explore having an error message that says that. (Is this the problem, David?)
gregnoel said at 2008-11-21 16:40:38
Bug party triage. Most likely a toolchain issue, so add keyword and consolidate with the related issues.
gregnoel said at 2008-12-26 13:20:23
Adjust triage of issues.
gregnoel said at 2009-02-22 12:30:53
Bug party triage. Accumulate issues with this underlying problem as dups of a common base issue.
*** This issue has been marked as a duplicate of 863 ***
gregnoel said this issue is a duplicate of #863 at 2009-02-22 12:30:53.
The text was updated successfully, but these errors were encountered:
This issue was originally created at: 2008-01-28 00:30:48.
This issue was reported by:
cournape
.cournape said at 2008-01-28 00:30:48
gregnoel said at 2008-04-14 12:36:24
garyo said at 2008-10-29 18:48:36
gregnoel said at 2008-11-08 18:32:12
gregnoel said at 2008-11-21 16:40:38
gregnoel said at 2008-12-26 13:20:23
gregnoel said at 2009-02-22 12:30:53
gregnoel said this issue is a duplicate of #863 at 2009-02-22 12:30:53.
The text was updated successfully, but these errors were encountered: