From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Problem Compiling Source Code From Unix
Date: Mon, 18 Sep 2017 15:56:00 -0000 [thread overview]
Message-ID: <4d2c1f80-99ef-99dd-e7cd-de17cb0cd5ec@t-online.de> (raw)
In-Reply-To: <1594208380.1685699.1505747601936@mail.yahoo.com>
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
next prev parent reply other threads:[~2017-09-18 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1594208380.1685699.1505747601936.ref@mail.yahoo.com>
2017-09-18 15:18 ` Graham Laight via cygwin
2017-09-18 15:56 ` Hans-Bernhard Bröker [this message]
2017-09-18 17:35 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d2c1f80-99ef-99dd-e7cd-de17cb0cd5ec@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).