Can RPM packages be installed into Cygwin?
De-Jian Zhao
dejian.zhao@gmail.com
Tue Apr 10 06:03:00 GMT 2012
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
More information about the Cygwin
mailing list