Newsgroups: comp.windows.ms
Path: utzoo!utgpu!watserv1!daemon
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Subject: Re: Link problems with MS-C 5.1 and MKS (was: Re: MessageBox problem)
Message-ID: <1990Sep27.183646.5845@watserv1.waterloo.edu>
Sender: daemon@watserv1.waterloo.edu
Organization: University of Waterloo, WATMIMS Research Group
References: <1990Sep12.043315.10404@Neon.Stanford.EDU> <1990S <767@tuura.UUCP> <7928@milton.u.washington.edu> <807@aut.UUCP>
Date: Thu, 27 Sep 90 18:36:46 GMT
Lines: 24

Norbert Bladt <bladt@hslrswi.UUCP> writes:
> efowler@milton.u.washington.edu (Eric Fowler) writes:
>>	I have been fighting a losing battle with the MSC 5.1 linker for
>> several days now.  I have some windows code that compiles, links, [...]
>> The error returned by the linker is always "Warning:No stack segment",
>> followed by:"Unresolved external:", and either 23 or 36 functions.  The

> Do you use the MKS shell at home and not at work ?
> I had a lot of problems with accessing environment variables from programs
> compiled and linked with MS-C 5.0 if the MKS shell was used.
> The placement of environment variables is NON-STANDARD DOS with the
> MKS shell (c.f. the special posting of RCS for MKS users in c.b.i.p !).

This is not true.  The environment can be accessed just fine --- as long as
you remember to EXPORT your variables from the shell (remember, this is
Korn shell!).  As to the separate RCS posting --- the MKS version is the
same as the standard one, except that it understands slashes as well as
backslashes in pathnames.

In any case, I do all my Windows development using MKS Toolkit, and I have
had ZERO MKS-related problems.

[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ "i don't even know what street canada is on"               -- al capone ]