Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!tumuc!lan!rommel
From: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Newsgroups: comp.windows.ms
Subject: Re: 3.0 SDK problems
Message-ID: <3543@tuminfo1.lan.informatik.tu-muenchen.dbp.de>
Date: 23 Jul 90 17:20:35 GMT
References: <26093@usc.edu>
Sender: news@lan.informatik.tu-muenchen.dbp.de
Reply-To: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Organization: Inst. fuer Informatik, TU Muenchen, W. Germany
Lines: 29

In article <26093@usc.edu> papa@pollux.usc.edu (Marco Papa) writes:
>3.  The major problem is with the 5.10 linker.  It just plain doesn't
>work.  It doesn't seem to be able to pick up ANY of the Windows library
>symbols and tells me that all the ones I use (174) are undefined, and
>then aborts.

>Note that I made all the appropriate changes to the .INF file (add the EXETYPE
>directive), and use the "recommended" compiler line:

>CL -c -AM -Gsw -Os -Zpe fname.c

>Has anybody gotten the 5.10 Linker to work with the 3.0 SDK?

>-- Marco

Hey, look at your C 5.10 distribution disks. You should find there two
copies of LINK.EXE. One is the OLDOLDOLDOLD 3.65 DOS-only linker which
cannot be used to create segmented-executables. The other one is 5.0.17
(or so) and can be used (I do this every day ...)

LINK4 is just another copy of this new linker. It says
"Segmented Executable Linker" in the COpyright message.

Kai Uwe Rommel
--
/* Kai Uwe Rommel
 * Munich
 * rommel@lan.informatik.tu-muenchen.dbp.de
 */