X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fZ9Asal11xxbNJwo
	ZS/wbCjcQ6zqM+mbMuRC2yjwQWxNNxUPG0N+llq9+T07PFqGmIIt03GMIZ20sS6x
	v7Y54xb3igCW39eoHZagVK3O4WzlHvincGMdBaIlgMaEOzF2rFsYdc1VTOxv/6aJ
	WCLtbZKuCVvHVL7qu15hxccvVAI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=wX7ku3/q+uFQy6wdxqHVEN
	Su98Q=; b=YhqAvenTg1oR/rZK0MUFifMkKFzKlV4VnSq8BdqXFVv3kwkbFbAQAw
	Tf3moRGboV2ZTGPeyNKXmznlSIyjFSw1ONp38tvQTSfkOijQGKKIIYoG05MDC+dP
	/8aS7uJiBe9+IXpjevgwy6B1x/q9qbvNJac5vlOjatDY7iNZb/vK0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*M:online, 18092017, 18.09.2017, H*r:172.20.26
X-HELO: mailout02.t-online.de
Subject: Re: Problem Compiling Source Code From Unix
To: cygwin@cygwin.com
References: <1594208380.1685699.1505747601936.ref@mail.yahoo.com> <1594208380.1685699.1505747601936@mail.yahoo.com>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker@t-online.de>
Message-ID: <4d2c1f80-99ef-99dd-e7cd-de17cb0cd5ec@t-online.de>
Date: Mon, 18 Sep 2017 17:56:08 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1594208380.1685699.1505747601936@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Am 18.09.2017 um 17:13 schrieb Graham Laight via cygwin:
> Hi Everyone,
> 
> I am trying to compile some SAT solvers, which all come as Unix source-code bundles. I have installed Cygwin at c:\cygwin, and added c:\cygwin\bin to my Windows path.

Unforturnately, that's already the point at which you strayed from the 
optimum path.  Cygwin provides, to the best of everyone's ability, an 
entire Unix _environment_.  And that means you'll usually have to enter 
that environment, not just pick things out of it from the outside.

In other words: no, the Cygwin bin directory should not usually be in 
your Windows PATH.  It can be done that way with sufficient insight into 
the consequences, but you should stay away from that can of worms for now.

> Lingeling came with the following instructions:
> 
> configure && make
> 
> Once I realised this translates to...
> 
> sh configure.sh && make

Actually, no such translation would have been necessary.  The general 
idea is that you would be doing this from inside the Cygwin console 
environment (i.e. click on that icon the installer created), and then 
such original Unix command lines will actually just work, without your 
needing to translate anything.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

