Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!umriscc!mcs213k.cs.umr.edu!jeffj From: jeffj@mcs213k.cs.umr.edu (Jeff Jenness) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Help using f2c with Borland C++ Summary: Problems with f2c and Borland C++ Message-ID: <2863@umriscc.isc.umr.edu> Date: 27 Jun 91 15:18:00 GMT References: <91174.123837HAN@FRECP12.BITNET> <5147@lib.tmc.edu> Sender: news@umriscc.isc.umr.edu Followup-To: comp.binaries.ibm.pc.d Organization: University of Missouri - Rolla Lines: 48 In article <5147@lib.tmc.edu> dfenyes@thesis1.med.uth.tmc.edu (David Fenyes) writes: >In article <91174.123837HAN@FRECP12.BITNET> you write: >> I am trying to use f2c (the Fortran 77 -> C[++] translator) with the >>Borland C++ compiler, and seem to have setup problems. After tweaking the >>command line switches, I have been able to run f2c and bcc on my Fortran code. > >I'm curious to know the problems you had (Was it the name table size?) > I have compiled the f2c libraries with Borland C++ and been able to run fortran programs that do not use formatted IO. I have not examined the problem in any great depth but feel it can be resolved by adjusting the code in the libraries. What concerns me is that the f2c translator is giving me an error on the following program: program test logical bool integer a data a,bool/1,.TRUE./ open(6,FILE='con') print*, 'BOOL = ',bool print*, 'A = ',a end The translator dies with the following message: Compiler error at line 12 of test.f: malloc(32006) failure! I have found two changes that will cause the translator to accept it: 1) comment out the data statement 2) take the strings out of the print* statements I felt that others using f2c would be interested in this and, seeing that David (the porter) reads this group, David would be kind enough to help out (even provide a fix?). If I am able to fix the library problems (time permitting), I will post. -- Jeff Jenness University of Missouri - Rolla jeffj@cs.umr.edu