From: Bob Kematick Newsgroups: comp.os.msdos.djgpp Subject: RHIDE with Fortran Date: Tue, 26 May 1998 15:25:37 -0500 Organization: AT&T WorldNet Services Lines: 40 Message-ID: <6kf4n2$gf0@bgtnsc02.worldnet.att.net> NNTP-Posting-Host: 12.68.173.226 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk This is a bug report for RHIDE Version 1.4 (Sep 30 1997 23:06:59) I am running MS-DOS 7.0 (Windows 95) Important environment variables: PATH=d:\djgpp\bin;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOS;C:\;C:\BIN;E:\GNU\BIN;C:\DOS\4DOS DJGPP=d:/djgpp/djgpp.env LFN=y INFOPATH=d:/djgpp/info;d:/djgpp/gnu/emacs/info LOCALEDIR= LANGUAGE= SHELL= COMSPEC=C:\DOS\4dos\4dos.com DJSYSFLAGS= My problem is the following: ============================ This is a very small matter. I use RHIDE with Fortran (g77) projects. It seems that in the link step , the libraries are linked in the wrong sequence. For example, a "myprog.f" program compiles and links as follows : g77 -g -c myprog.f -o myprog.o gcc myprog.c -o myprog.exe -lm -lf2c The last step should be : gcc myprog.c -o myprog.exe -lf2c -lm The sequence really does make a difference, and I have been bitten at times. The docs for f2c also warn about this. It is an easy enough matter to redefine RHIDE_TYPED_LIBS.f in rhide.env, but it seems to me that default should perhaps be changed in future editions.