Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@sourceware.cygnus.com>
List-Subscribe: <mailto:cygwin-subscribe@sourceware.cygnus.com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin@sourceware.cygnus.com>
List-Help: <mailto:cygwin-help@sourceware.cygnus.com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Wed, 25 Aug 1999 12:05:12 -0400
To: "cygwin@sourceware.cygnus.com" <cygwin@sourceware.cygnus.com>
Subject: Re: Re: Newbie C Questions
Message-ID: <19990825120512.A1508@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: "cygwin@sourceware.cygnus.com" <cygwin@sourceware.cygnus.com>
References: <DMDLODHCLHACCAAA@my-deja.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <DMDLODHCLHACCAAA@my-deja.com>; from  Clark Sims  on Wed, Aug 25, 1999 at 04:24:53AM -0700

On Wed, Aug 25, 1999 at 04:24:53AM -0700,  Clark Sims  wrote:
>On Tue, 24 Aug 1999 22:54:10   Chris Faylor wrote:
>>On Tue, Aug 24, 1999 at 09:58:00PM +0200, Michael Hirmke wrote:
>>>>I use the Watcom compiler, but I can't get it to
>>>>compile with the Cygnus port of GCC. The include
>>>>file conio.h is not being found. conio.h exists
>>>>in one of the subdirectories of Cygnus, but GCC
>>>
>>>Your setup seems to be, uhm a bit chaotic.
>>>Please paste the output of
>>>   cygcheck -s -v -r 
>>>to a mail to this list. Perhaps we can see, what's
>>>going wrong.
>>
>>Actually, I'm confused by the wording here.  How do you get a
>>Watcom compiler to compile using a cygnus port of gcc?
>
>wcl386 mypg.c

And, that compiles mypg.c with the Watcom compiler.  What does cygwin
have to do with this?

>>What does Watcom have to do with Cygwin gcc?
>
>They both produce WIN32 code, which runs well under an NT system.  I
>like to run compilers in parallel as a check on one another.  The
>Watcom compiler is good because it is pretty ANSI compilent, and it is
>very stable (few bugs).  Too bad Sybase has killed it.  Sybase's
>actions are responcible for me switching to freeware and openware.

Uh huh.  I'm still not getting what Watcom has to do with anything.
If you're having a problem accessing an include file via gcc, then
this has nothing to do with Watcom.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

