public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Robert May <tpibob@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re error after installing cygwin64 4.3.1.1
Date: Tue, 26 Jan 2016 17:25:00 -0000	[thread overview]
Message-ID: <BAY175-W31F6CA55D18FD6CD087A34ADC70@phx.gbl> (raw)

Marco
The choice of using usr/local/bin was the way to go according to the INSTALL instructions with most of the programs.

some use ./confire    -    make     -     make install

some use      make     make install


I think one used just make and one used Build.

If I remember the wording correctly "they say" copy your "package" "program" to the usr/local/bin foler and then in cycgwin use cd drive:/cygwin64/usr/local/bin and the use the followinf commands or script to install the package/program

Bob



htslib configure - make - make install ok
>
> samtools configure ok
>
> Robert@DESKTOP-14EL82S /usr/local/bin/samtools-1.3

Personal preference: in general "/usr/local/bin" is not the place
that I will use as build area.

> $ ./configure

can you please clarify what is your problem ?

I tried to build samtools-1.3 and it has at least two issue
for a porting to cygwin:

- on Makefile there is a -rdynamic that does not work on cygwin
- the package require expl and logl that are not yet available in cygwin



Regards
Marco

 Bob May
DNA Projects I2b L415, I2c L596 HG, Spriggs of Cleve SA Family & Tyler Surname and ISOGG YTree 		 	   		  
--
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

             reply	other threads:[~2016-01-25 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 17:25 Robert May [this message]
2016-01-27  7:21 Robert May
2016-01-27 11:23 ` Marco Atzeri

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=BAY175-W31F6CA55D18FD6CD087A34ADC70@phx.gbl \
    --to=tpibob@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).