Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpsrla!hpsrlc!darrylo
From: darrylo@hpsrlc.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C linking Large models
Message-ID: <3320055@hpsrlc.HP.COM>
Date: Thu, 17-Sep-87 11:03:10 EDT
Article-I.D.: hpsrlc.3320055
Posted: Thu Sep 17 11:03:10 1987
Date-Received: Sat, 19-Sep-87 17:46:27 EDT
References: <7871.1609.forumexp@mts.rpi.edu>
Organization: HP Network Measurements Div - Santa Rosa, CA
Lines: 25

In comp.sys.ibm.pc, forumexp@rpitsmts.CE.HP.COM writes:

>       I've heard that Turbo C has problems linking large memory model
>    code. Is this bug in all versions, or only the earliest releases,
>    and how do I know if I'm affected.
> 
>        My TC does not have the infamous (floating-point division"
>    error. Any other problems I should know about?
> ----------

     The last I've heard about bugs in TC (and it's been a month or two since
I've checked into TC bugs), there is a bug involving TLINK and programs whose
code requires more than 64K.  Basically, TLINK has trouble linking programs
whose code space occupies more than 64K.  A workaround is to use the
Microsoft linker, LINK (note that, if you don't use the integrated
environment or TCC to compile/link your program, you will have to
explicitly tell the linker what Turbo C library files to use).

     -- Darryl Okahata
	{hplabs!hpcea!, hpfcla!} hpsrla!darrylo
	CompuServe: 75206,3074

Disclaimer: the above is the author's personal opinion and is not the
opinion or policy of his employer or of the little green men that
have been following him all day.