Xref: utzoo comp.lang.c:7555 comp.sys.ibm.pc:12382
Path: utzoo!mnetor!uunet!mcvax!cernvax!ethz!zu
From: zu@ethz.UUCP (Urs Zurbuchen)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: TurboC: Stupid Linker ?
Message-ID: <307@bernina.UUCP>
Date: 23 Feb 88 07:46:47 GMT
References: <2622@i.cc.purdue.edu>
Reply-To: zu@bernina.UUCP (Urs Zurbuchen)
Organization: ETH Zuerich, CS Department, Switzerland
Lines: 13

In article <2622@i.cc.purdue.edu> aja@i.cc.purdue.edu (Miek Rowan) writes:
>> I had this problem also last summer (Version 1.0).  I called the Borland
>> folks.  They told me what was wrong and how to cope with it.  The problem
>> is Borland's tlink.  The solution that the Borland folks recommended is
>> to use a recent version of Microsoft's link.  I did and it worked.  Keep
>> in mind that without using tlink, you have to use command line mode

I read in the manual to Data&Windows that the Turbo-C linker tlink does NOT
report unresolved externals. Can anybody confirm? Or proof the contrary
(which would be much better for Borland).

		Regards,
		...urs