Xref: utzoo comp.os.msdos.programmer:5212 comp.lang.c:39441
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!hp4nl!rivm!epiren
From: epiren@rivm.nl (I.A.Kreis)
Newsgroups: comp.os.msdos.programmer,comp.lang.c
Subject: Re: Summary of C Compilers from INFOWORLD
Message-ID: <1991May21.175117.4101@rivm.nl>
Date: 21 May 91 17:51:17 GMT
References: <28483@uflorida.cis.ufl.EDU> <3992@ssc-bee.ssc-vax.UUCP>
Sender: news@rivm.nl
Organization: Rijksinstituut voor Volksgezondheid & Milieuhygiene, Bilthoven,NL
Lines: 13

In article <3992@ssc-bee.ssc-vax.UUCP> coy@ssc-vax.UUCP (Stephen B Coy) writes:
> . . . . You have to change the LIB environment variable to
>reflect whatever memory model you currently want.  

You don't have to specify the LIB variable. You don't have to link either.
It is a compiler, not a linker. They DO give away alinker with the compiler
package, which in my case works well. The LMB (linker) accepts full pathnames,
which can be easily found in the first of T4FM's, but I agree, 
just experimenting with it is a quicker way to find out. Flaming is even
quicker.

Adriaan van Kessel
epiren@rivm.nl