This is what comes up when I type gfortran -v in MobaXterm: Using built-in specs.ĬOLLECT_LTO_WRAPPER=/bin/./lib/gcc/i686-pc-cygwin/4.9.2/lto-wrapper.exeĬonfigured with: /cygdrive/i/szsz/tmpp/gcc/gcc-4.9.2-3.i686/src/gcc-4.9.2/configure -srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.2-3.i686/src/gcc-4.9.2 -prefix=/usr -exec-prefix=/usr -bindir=/usr/bin -sbindir=/usr/sbin -libexecdir=/usr/libexec -datadir=/usr/share -localstatedir=/var -sysconfdir=/etc -libdir=/usr/lib -datarootdir=/usr/share -docdir=/usr/share/doc/gcc -htmldir=/usr/share/doc/gcc/html -C -build=i686-pc-cygwin -host=i686-pc-cygwin -target=i686-pc-cygwin -without-libiconv-prefix -without-libintl-prefix -libexecdir=/usr/lib -enable-shared -enable-shared-libgcc -enable-static -enable-version-specific-runtime-libs -enable-bootstrap -enable-_cxa_atexit -with-dwarf2 -with-arch=i686 -with-tune=generic -disable-sjlj-exceptions -enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++ -enable-graphite -enable-threads=posix -enable-libatomic -enable-libgomp -disable-libitm -enable-libquadmath -enable-libquadmath-support -enable-libssp -enable-libada -enable-libjava -enable-libgcj-sublibs -disable-java-awt -disable-symvers -with-ecj-jar=/usr/share/java/ecj. Manually launch the executable thru the debugger. Gfortran is now recognized, but when I try to compile, no executable is produced (that I can find).
I tried installing gfortran in MobaXterm instead by using apt-cyg install gcc-fortran. This document describes GNU Guix version 1.3.0, a functional package management tool written for the GNU system.
I installed gfortran and it works in the windows terminal, but MobaXterm does not find it (i.e. However, I am using MobaXterm and I cannot get it to work there.
My OS is windows, and I've gotten gfortran downloaded and working in the windows terminal. However, the addon installer is now stuck on 'Registering Support for MinGW-w64 compiler 4.9. I am having trouble installing gfortran on my computer. After I added the ZIP files to the target folder I tried to use the addon installer again, and I got past what I got stuck on previously.