Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucsd!ames!sun-barr!texsun!texbell!sequoia!rpp386!jfh
From: jfh@rpp386.Dallas.TX.US (John F. Haugh II)
Newsgroups: comp.unix.wizards
Subject: Re: Weird problem with C compiler under SCO - I can't believe it!
Message-ID: <17022@rpp386.Dallas.TX.US>
Date: 17 Sep 89 14:26:06 GMT
References: <71@promark.UUCP> <11101@smoke.BRL.MIL>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: TrishTrash Readers, Inc.
Lines: 20

In article <11101@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>In article <71@promark.UUCP> mark@promark.UUCP (Mark J. DeFilippis) writes:
>>Any constructive comments?  Has this been seen before?
>
>Yeah.  Some MS/DOS C compilers think "cdecl" is a C keyword,
>meaning "use C linkage for this function even though a global
>compile switch says to use Pascal linkage".  It's a crock.
>
>If you're lucky, you can do what on UNIX would be expressed as
>"cc -Dcdecl=Xcdecl" to work around the problem without having
>to do a lot of editing.

This option can be turned off by editing /etc/default/cc and
removing the 'e' from the FLAGS= line.  [ Or he could add
-Dcdecl=Xcdecl if he wants the other Intel extensions ]
-- 
John F. Haugh II                        +-Quote of the month club: ------------
VoiceNet: (512) 832-8832   Data: -8835  |  It's not that important,
InterNet: jfh@rpp386.cactus.org         |      it's only USENET.
UUCPNet:  {texbell|bigtex}!rpp386!jfh   +--------------     -- Rich $alz   ----