Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"machine man" <machineman AT acmecity DOT com>
Message-Id:	<32DCEE5D73E34D11786400807CFBD62A@machineman.acmecity.com>
Date:	Fri, 9 Jun 2000 14:54:54 -0700
X-Priority:	Normal
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	General newbie, Cygnus, and GNU compiling questions
X-Mailer:	Web Based Pronto
Mime-Version:	1.0

Hi all,

I just downloaded the latest version of Cygwin, and I have a couple of questions.

First off, does vi exist for Cygwin?  I hate it with all my heart, yet I'm drawn to it at the same time like a moth to fire...  I need to talk to a therapist.

Secondly, I tried compiling some GNU utilities from ftp.gnu.org with limited success.  I was able to compile 'which', but I tried to compile 'make' version 3.79 and it cakked.  More specifically, it didn't seem to like the \ to extend a line within a #.  I did see an entry in the mailing list concerning make 3.79 but I didn't quite understand it... Does Cygwin need a different compile for make, or can it compile the ftp.gnu.org version?  Also, I tried to issue the "setup make" but the binary still seems to be version 3.77.

Also, the make included with the distribution doesn't seem to like \ in makefiles either.  This is strange because the exact same code I tried to compile works fine using gnu make on Solaris.

This is a more general question.  Are there any hints, FAQs or URLs that deal with porting software from UNIX with Cygwin, ie. specific issues to watch out for?

I'm experimenting with trying to port our company's major product using CYGWIN for our Win32 platform.  I was able to compile it using gcc on Solaris Intel so I think gcc is fine, but I don't know if there are any specific gotchas associated with CygWin.  Right now, we have 2 different code bases for our UNIX and Win32 platforms, so if I could somehow get everything to run under the same codeline, it would cut down on a lot of problems.

Also does anyone have any ideas with speed differences between binaries compiled with Cygwin gcc vs. MSVC?

Thanks

Sent by AcmeCity Mail

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -