Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!b-tech!zeeff
From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Replacing a Microsoft C library routine
Keywords: C, Microsoft, link
Message-ID: <5046@b-tech.ann-arbor.mi.us>
Date: 9 Jan 89 00:16:19 GMT
References: <5041@b-tech.ann-arbor.mi.us> <2521@stiatl.UUCP>
Reply-To: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff)
Organization: Branch Technology Ann Arbor, MI
Lines: 46


>>For a few programs I've written, I believe that I need to disable 
>>calls to chkstk (I'm calling microsoft C routines from an interrupt 

>>The best solution seems to be to write a null chkstk routine and link 
>>it in.  This creates an error message about multiply defined symbols.  

In article <2521@stiatl.UUCP> john@stiatl.UUCP (John DeArmond) writes:
>Use the /NOE linker switch.  The multiply defined error message the 
>linker generates tells you to use this switch.  
>
>RTFM .. er ... RTFcrt   :-)

I have of course and /NOE doesn't do a bit of good.  You still get a 
symbol defined more than once error.  

>>I've tried removing chkstk from the library with -chkstk, but this seems
>>to remove some other needed routine or variable (STKHQQ).

>I'd recommend that you simply include an empty definition of _chkstk() for
>normal conditions and let the compiler include the call.  I've found that this
>call is invaluable for debugging.  Since it is called immediately before the

Thats what I'm trying to do.  Do you have code that replaces _chkstk() and
links without errors (MSC 5.0).

















-- 
  Jon Zeeff			zeeff@b-tech.ann-arbor.mi.us
  Support ISO 8859/1		zeeff%b-tech.uucp@umix.cc.umich.edu
  Ann Arbor, MI			umix!b-tech!zeeff