Hi, everyone,
This is a follow up of my last reply in which I mentioned a confliction in
configure.
I think I know why this happened. On Oct 02, Vitaliy checked in new
configure and configure.in. But I used autoconf to generate a configure
from configure.in after last check out, so my configure has a newer time
stamp that the one in CVS. It caused confliction when I try to update
after Vilatley checked in his changes. So the problem was on my side.
However, it seems annoying that using autoconf after checking out from cvs
will potentially cause confliction. Did I miss any steps?
Chi
On Fri, 11 Oct 2002, Timothy Smith wrote:
>
> Hello People,
>
> I am going to try and get the version of BlastLib2
> (version 2) in CVS inline with what is being used and working.
> A few observations. The libBlast.so used by the spuds is
> dated Sept 26, and is 5.4 MegaBytes. I think this is the one
> people are using.
>
> All other versions, includeing the one from cvs
> (cvs up -r v2) at about 2.4-2.6 MegaBytes. Something major
> must be different.
>
> Also I am a bit out of the loop. Clearly there are
> some scripts which are current and critical, and some which
> are dated and my not reflect the important features of libBlast.C .
> So what are they? I am starting by assuming that
>
> /home/blast/blast/commis/phase1/ntuple.C
>
> is still a critical piece.
>
> I think getting cvs right again is something I can do
> from Dartmouth, but I need to know where things stand first.
> If you email me, send you phone number and I'll call you -
> or you can call me.
>
> Tim
> ____________________________________________________________________
> Timothy Paul Smith Assistant Research Professor
> Dartmouth College timothy.p.smith@dartmouth.edu
> Department of Physics and Astronomy -or- tim_smith@mit.edu
> 6128 Wilder Lab.
> Hanover, New Hampshire 03755 tel: (603) 646-9346
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST