Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!physiol.su.OZ.AU!john From: john@physiol.su.OZ.AU (John Mackin) Subject: Re: Please Help with FORTRAN Message-ID: <1994Oct7.222526.6011@physiol.su.OZ.AU> Organization: The Land of Summer's Twilight References: <1994Sep27.233949.26036@cae.daikin.co.jp> <36kqbs$5fe@pdq.coe.montana.edu> Date: Fri, 7 Oct 1994 22:25:26 GMT Lines: 23 In article <36kqbs$5fe@pdq.coe.montana.edu>, nate@bsd.coe.montana.edu (Nate Williams) writes: > It's possible that the version of f2c that FreeBSD is using is older and > has bugs in it. It should be updated to a newer version. Anything's possible, but I'd suspect the original poster's code here. A friend of mine ported a fair-ish quantity of _exceptionally_ nasty (read: unorthodox, stress-test-your-implementation) Fortran to a FreeBSD machine's f2c a few weeks ago, and after resolving a few minor differences in names of intrinsics (which kept it from linking -- i.e. couldn't be responsible for runtime problems) it ran flawlessly. He was impressed; so was I. Yes, the supplied f2c _could_ have bugs, but from here it looks pretty darn good. One question: the original poster mentioned "g++". Whaaat? We _certainly_ didn't try to link Fortran and C++... as Mary says in _The American Way,_ `I didn't know they could.' -- John Mackin <john@physiol.su.oz.au> Knox's box is a 286. Fox in Socks does hacks and tricks Knox's box is hard to fix. To fix poor Knox's box for kicks.