Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!bcm!lib!thesis1.med.uth.tmc.edu From: dfenyes@thesis1.med.uth.tmc.edu (David Fenyes) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Help using f2c with Borland C++ Message-ID: <5157@lib.tmc.edu> Date: 28 Jun 91 03:19:25 GMT References: <91174.123837HAN@FRECP12.BITNET> <5147@lib.tmc.edu> Sender: usenet@lib.tmc.edu Organization: University of Texas Medical School at Houston Lines: 30 Nntp-Posting-Host: thesis1.med.uth.tmc.edu In article a_rubin@dsg4.dse.beckman.com (Arthur Rubin) writes: >(2) You need to compile the libraries with the /Zl option to remove the >standard library names. >As a temporary fix for (2), you could supply empty libraries ?libce.lib so that >the link won't fail. (I think one reason the libaries are there explicitly is >to prevent you from linking small and large model programs together; they won't >work, and this causes the linker to produce an error message.) Thanks for the wisdom :-) Folks--read the above. Meanwhile, I'll recompile the libs. >(3) The compiler DOES generate different code, as well as generating different >library names, depending on the /FP flag. (I think /FPc and /FPc87 generate >identical code.) I'm afraid you either have to supply your own copies of MSC's >libraries (probably written in assembler), or be VERY careful in using floating >point. I used the 'use if detected' option for the libraries. That way, only two were needed & the zip file was not overwhelming. However, maybe providing two sets of libraries, one for 80x87, and one for inline emulation would be more portable. Give me feedback, & I'll do it here & repost, and possibly save the rest of you hours of compilation time :-) David. -- David Fenyes dfenyes@thesis1.med.uth.tmc.edu University of Texas Medical School Houston, Texas