I loaded patch 247 (or something close to it) on all the boxes, and then I
upgraded all of them. I've done various update processes.
1) erase all the source code from scratch, and downloaded patch-299, and
went through the autogen.sh, configure, make, make install
2) used the idea of the build directory and ran autogen.sh, configure, make
install
3) used the "tla update" and then configure, and make install.
I changed build methods as I found faster ways to build the code, and I
assume that the
build process is putting all the right files in the right place. Maybe it is
a Makefile issue so
there was some older object files around. Method #1 above seemed to be the
safest, best,
and cleanest method, but also the slowest. I *assumed* that all 3 methods
above resulted
in the same end product. I don't know how to check what I've got outside of
"tla tree-id", and
they all say patch-299.
From: "Amar S. Tumballi" <amar@xxxxxxxxxxxxx>
To: "DeeDee Park" <deedee6905@xxxxxxxxxxx>
CC: gluster-devel@xxxxxxxxxx
Subject: Re: Core BT
Date: Thu, 12 Jul 2007 11:05:24 +0530
Hi DeeDee,
Can you confirm this bug is from patches after 292 (patch-292,
mainline--2.5)? because the code where you got the segfault is removed from
that version (removed as in '#if 0'). (or are you sure, you did a 'make
install'?)
This should not be happening in any patches after that (patch-292+).
-amar
On 7/11/07, DeeDee Park <deedee6905@xxxxxxxxxxx> wrote:
_________________________________________________________________
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
Amar Tumballi
http://amar.80x25.org
[bulde on #gluster/irc.gnu.org]
_________________________________________________________________
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_2G_0507
