From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: bwa error running Make and Make Install after installing update 2.4.1.1 to Cygwin64
Date: Thu, 28 Jan 2016 14:24:00 -0000 [thread overview]
Message-ID: <CAEhDDbBOKBoH9D-9eFw6CU9UTD2GKE5us7BWRqYyvz_Yq0byCg@mail.gmail.com> (raw)
In-Reply-To: <BAY175-W14B0BA99679BF1F7A0EF33ADC70@phx.gbl>
On Mon, Jan 25, 2016 at 10:03 PM, Robert May wrote:
> Robert@DESKTOP-14EL82S /usr/local/bin/bwa-0.7.12
> $ ./configure
> -bash: ./configure: No such file or directory
>
> Robert@DESKTOP-14EL82S /usr/local/bin/bwa-0.7.12
> $ make
> make: Nothing to be done for 'all'.
>
> Robert@DESKTOP-14EL82S /usr/local/bin/bwa-0.7.12
> $ make install
>
> make: *** No rule to make target 'install'. Stop.
Hi Robert,
What is your Cygwin question?
Assuming that bwa is https://github.com/lh3/bwa , you really should
have read the readme. It makes no mention of configure nor does it
mention 'make install'.
Updating Cygwin has nothing to do with it; I get the same errors with
Cygwin 2.3.1 (unsurprisingly, since there is no configure and no
"install" target in the makefile).
BTW, /usr/local/bin is not the best place for a source tree.
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
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
prev parent reply other threads:[~2016-01-28 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 21:30 Robert May
2016-01-28 14:24 ` Csaba Raduly [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=CAEhDDbBOKBoH9D-9eFw6CU9UTD2GKE5us7BWRqYyvz_Yq0byCg@mail.gmail.com \
--to=rcsaba@gmail.com \
--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).