We have been trying to handle problems from all corners...On 32-bit Linux systems IN GENERAL, we build libz and libbz2 from source. The idea is that 32 bit systems are usually older, and we occasionally find people who don't have them available as dynamic libraries.
You can safely disable this by removing "ext" from the makefile subdirectories of libs/Makefile. This target normally does nothing on 64-bit systems, but on 32-bit systems it will download sources, unpack and build them.
The Judy code is required right now, and you will want it. We have not tried linking against an installed version, but it should work. To do this, you would disable the libs/klib/judy sub-directory and change libs/klib/Makefile to link against your systems' judy libraries with a normal "-ljudy" rather than "-sjudy".
We can also try to put together a cleaner build for you on this end, if you are willing to wait. The reason is that your users are going to need the latest code, especially the latest external schema functions, in order to work with SRA. It is important to push the version ahead.
So please try with the information in this email, and if it doesn't solve ALL your problems, we'll put together a source tarball for you that is specifically clean for dynamic builds. Currently our dependencies are:
libz libbz2 libjudy libxml2 (loaders only) libhdf5 (pacbio-load only) SRA Toolkit Team At 10:03 AM -0500 1/10/12, Charles Plessy wrote:
Le Mon, Jan 09, 2012 at 11:54:04AM -0500, SRA Toolkit Development Group a écrit :$ make release dynamic and then things should be as you were expecting. "make release" will create symlinks within $OUTDIR to binaries and libraries. You are going to need to move up much closer to the current release now that we are building cSRA objects within NCBI's archive. We expect to release 2.1.9 early this week. Older code bases will not be able to manage the schemas found within new object types.Thank you very much. "make release dynamic" worked perfectly.I have now updated to 2.1.7a, as I noted that 2.1.8 introduced some third-partyfiles that I did not have time to review fully. Some of them are related to zlib and libbzip? Would it be safe to delete them altogether if I onlymake dynamic builds ? The other are related to the Judy library. Do you thinkI can link safely to Debian's version (1.0.5) ? Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan _______________________________________________ Sra-tools mailing list Sra-tools@ncbi.nlm.nih.gov http://www.ncbi.nlm.nih.gov/mailman/listinfo/sra-tools