Re: [BLAST_ANAWARE] static linkage of nsed and lrn

From: zhangchi (zhangchi@general.lns.mit.edu)
Date: Mon Jun 30 2003 - 10:29:43 EDT


I am not sure if trying the static link is worthy of the debugging time.
configure with prefix works and serves the purpose of envoking lrn without
libBlast.so in current directory or in load path.

The only draw back is the dependence. if libBlast.so is recompiled, it may
be incompatible with the lrn one copied to somewhere else earlier.

On Sun, 29 Jun 2003, Tancredi Botto wrote:

>
> do not worry
> we are better off with root than without and it's me more than you that
> will do it. cheers
>
> -- tancredi
> ________________________________________________________________________________
> Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
> research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> On Sun, 29 Jun 2003, zhangchi wrote:
>
> >
> > Hi, Tancredi
> >
> > Since a certain time, staticly linking lrn and nsed became impossible and
> > after two hours I could not figure out why. It was once not a problem and
> > I do it all the time. I suspect it happened when we upgraded to a certain
> > version of Root.
> >
> > I HATE ROOT !!!!!!!!!!!!!!!!!!!!!!!
> >
> > however, to have a lrn/nsed that would work from any directory. It dose
> > not require static linkage. do the configure with --prefix
> >
> > ./configure --prefix=`pwd`
> >
> > then the linking to libBlast.so will follow absolute path. This can easily
> > be confirmed by:
> >
> > ldd lrn
> > > libBlast.so => /home/blast/blast/cvs_v3/BlastLib2/libBlast.so (0x40013000)
> >
> > this way, you can copy lrn to any place, it will find libBlast.so in the
> > path shown.
> >
> > Chi
> >
> >
> >
>



This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST