X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG
X-Spam-Check-By:	sourceware.org
Message-ID:	<4F83CD31.40507@gmail.com>
Date:	Tue, 10 Apr 2012 14:03:29 +0800
From:	De-Jian Zhao <dejian DOT zhao AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
CC:	warren AT etr-usa DOT com
Subject:	Re: Can RPM packages be installed into Cygwin?
References:	<4F7FEF5B DOT 5060206 AT gmail DOT com> <4F7FF6FB DOT 7070206 AT gmail DOT com> <4F810192 DOT 40806 AT gmail DOT com> <4F813482 DOT 2020101 AT gmail DOT com> <4F82FC50 DOT 50805 AT gmail DOT com> <4F838387 DOT 1070705 AT etr-usa DOT com>
In-Reply-To:	<4F838387.1070705@etr-usa.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

  It seems that the compilation under Cygwin is more complicated than 
expected.
Thank you for your explanation, Warren.

On 2012-4-10 8:49, Warren Young wrote:
> On 4/9/2012 9:12 AM, De-Jian Zhao wrote:
>> the compilation
>> always stopped at "checking python" even after python was installed.
>
> My wild guess based on no personal experience with BLAST+ is that 
> there is some linkage error here.  I'd have to try it myself (not 
> interested) or examine the config.log file (still not interested) to 
> figure out if this guess is correct.
>
> I'd bet there are more Cygwin-using BLAST+ users on the BLAST+ mailing 
> list than on the Cygwin list, so you'd have a better chance of getting 
> a solution by sending the config.log file to that list than continuing 
> to pursue this problem here.
>
> Instead of trying to start with RPM, I'd recommend figuring out how to 
> build BLAST+ to build from source first.  You need that experience to 
> help you build binary packages.
>
> I think you'll have an easier time learning to build a native Cygwin 
> package than trying to get the .src.rpm file to rebuild on Cygwin:
>
>     http://cygwin.com/setup.html
>
> That page gives several methods for building Cygwin packages.  I'd 
> recommend going with the Cygport option.  Cygport does fewer things 
> than RPM, so building .cygport files is easier than building RPM .spec 
> files.  (In Cygwin, much of the rest of what RPM does lives in 
> setup.exe and cygcheck.exe.)
>
> I doubt there's enough value in the existing BLAST+ .spec file to make 
> it an easier path for you than building a .cygport file from scratch.
>
>> Then what is [the rpm package] for?
>
> It is for people who wish to build a secondary packaging system on top 
> of Cygwin's native system.
>
> It doesn't magically port Linux RPM packages over for you.  You still 
> have to do that work yourself.  And, you have to do that work without 
> having the benefit of an ecosystem of existing RPM binary packages, 
> upon which that BLAST+ .spec file probably depends.
>

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

- Raw text -