Jonathan Wakely via Gcc-help wrote: > On Mon, 4 Nov 2024, 23:59 George Rinker via Gcc-help, <gcc-help@xxxxxxxxxxx> > wrote: > >> I've been having some problems getting my source code compiled with >> gfortran. In particular, I get inexplicable fatal errors with pointers >> to code lines that are legal and have compiled many times before, and >> the error messages are not informative and hang the command shell I'm >> using (cmd.exe). There seem to be problems with stderr, stdin, and >> stdout in the compiler, presumably due to incompatible terminal >> assignments. I've been writing Fortran programs continually for almost >> 60 years (since 1967), so it's not like I'm new at this. Is there a >> forum or something where I can get advice about this sort of thing? >> > > This mailing list is the right place, but I don't know how many of the > gfortran developers are subscribed here. You could try the > fortran@xxxxxxxxxxx list just to ask somebody to reply here. > > However, it sounds like the problem is with the Windows shell, so maybe the > issue lies with mingw, or whatever environment you're using to run GCC on > Windows. > I also still program in fortran and tear my hair out when moving to a new compiler version. The fortran I use is so old that it doesn't have library functions like stderr. I'm not sure what part of your build system is new (you mentioned that the code had compiled before) but that is where to look. I would try rolling back your setup to something that works and then move forward carefully. Though it is annoying, you can start by commenting out everything but the calls and declarations and see if you can get it to compile. I have never got fortran code to work with gdb so I print debug information using print*, and this has always worked. Once you get something that works you can start re-introducing statements until you find an issue. I'm sure most every programmer has done that before. It always does seem to work though it can be very tedious. You can also get fortran help at the code guru non-visual c++ forum. http://forums.codeguru.com/forumdisplay.php?9-C-(Non-Visual-C-Issues) I think that gnu compiles fortran as c anyway. At any rate, I have had fortran questions answered there. My programs are c++ programs where the fortran is now a function. I found it easier to let the c++ be the part that communicates with the rest of the world. LMH
