[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: BLAST+ speed & build issues


An update on this:

1) I do have a real user who raised the speed issue doing real analysis
but admitted his script was both unusual and poorly written (aligning
short sequences one at a time).

2) For Bio-Linux users I'm now providing ncbi-blast+-static as an
optional drop-in replacement for ncbi-blast+.  This takes the upstream
pre-compiled binaries as the "source" and just rearranges them into a
very large binary deb (amd64 only).  Of course I have no intention of
taking this monstrosity anywhere near Debian but you can have a peek at
it in Launchpad if you like:




On Fri, 2011-08-19 at 11:51 +0200, Karsten Hilbert wrote:
> On Fri, Aug 19, 2011 at 10:38:03AM +0200, Steffen M�ller wrote:
> > What is special about Debian is not only that there are binary packages.
> > We also have the means to let our audience recompile packages in a
> > sufficiently easy way.
> > 
> > Now, if you possibly say that getting towards a static variant is not
> > more difficult than some
> > 
> > LDFLAGS=-static dpkg-buildpackage -rfakeroot
> > 
> > then this would be rather stimulating. If it is not like this, could
> > we get it towards it? Those who need it static then shall compile it
> > themselves this way.
> The dynamically linked (or -dev or source-) package could even provide
> 	blast-compile_statically
> Karsten
> -- 
> GPG key ID E4071346 @ gpg-keyserver.de
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

To Err is human.
To Arrr is Pirate!

Reply to: