public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Graham Laight <gandtandb@yahoo.co.uk>,
	Graham Laight <gandtandb@yahoo.co.uk>,
	 cygwin@cygwin.com
Subject: Re: Problem Compiling Source Code From Unix
Date: Mon, 18 Sep 2017 17:35:00 -0000	[thread overview]
Message-ID: <533039322.20170918202306@yandex.ru> (raw)
In-Reply-To: <1594208380.1685699.1505747601936@mail.yahoo.com>

Greetings, Graham Laight!

> 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.

That was a wrong move.
Unless you exactly know what you are doing, and ready for the consequences,
adding Cygwin bins to windows PATH is a recipe for disaster.

> Lingeling came with the following instructions:

> configure && make 

> Once I realised this translates to... 

> sh configure.sh && make 

No, it is exactly ./configure && make, no translation.

> ...it was fine, and I am happily running Lingeling - which is a good SAT
> solver!

> Unfortunately, many of the other SAT solvers are based on MiniSat - and
> these all have the same instructions, which I cannot follow: 

> export MROOT=<minisat-dir>  (or setenv in cshell) 
> cd { core | simp } 
> gmake rs 

> I don't know what export MROOT means (or setenv).

It means you have to set the environment to a value. This is not Cygwin
specific.

> Then I do cd core (to get to the C:\Temp\MapleCOMSPS\core folder), and issue

> make rs

> I receive the error: 

> Makefile:4: /mtl/template.mk: No such file or directory 
> make: *** No rule to make target '/mtl/template.mk'.  Stop. 

> It cannot find included files in C:\Temp\MapleCOMSPS\mtl . I have also
> tried adding C:\Temp\MapleCOMSPS\mtl to the Windows path - but this didn't
> change anything.

> Apologies if this question has more to do with my lack of knowledge of
> compiling under Linux than it does with Cygwin - but it would mean a lot to
> me to be able to get the other SAT solvers working, so I would really
> appreciate guidance!

This has nothing to do with compiling at all, just the general Linux usage.

Try

    cd simp
    MROOT="$(dirname "$(pwd)")" make rs

> PS - further apologies if the list receives a duplicate of this message -
> but my Outlook mail is misbehaving.

Try a normal mail client.


-- 
With best regards,
Andrey Repin
Monday, September 18, 2017 20:07:47

Sorry for my terrible english...


--
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

      parent reply	other threads:[~2017-09-18 17:35 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
2017-09-18 17:35   ` Andrey Repin [this message]

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=533039322.20170918202306@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=gandtandb@yahoo.co.uk \
    /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).