I just sent email with the build processes I've used. The systems have had
older versions of gluster,
pre4, pre5.1, tla patch 24x, and patch-299, so it is definitely possible.
but this is beyond my understanding binary execution process. What should I
be looking for? I've seen variables like LD_LIBRARY_PATH, but that is the
extent of my understanding in this area.
I didn't do anything special in building the product. I take certain
assumptions that
the build process will force all new files and only the new files to be used
-- which sounds
like is a bad assumption. What is the "correct" thing I am looking for to
know I'm good.
From: "Anand Avati" <[EMAIL PROTECTED]>
To: "DeeDee Park" <[EMAIL PROTECTED]>
CC: [email protected]
Subject: Re: [Gluster-devel] Core backtrace - libc
Date: Thu, 12 Jul 2007 12:37:10 +0530
this is due to a mismatch between your 'glusterfs' binary and '
libglusterfs.so'. Please look into your installation (probably an old
libglusterfs.so is lurking somewhere in the library path)
thanks,
avati
2007/7/12, DeeDee Park <[EMAIL PROTECTED]>:
To answer your question, i'm not doing any test in particular when these
core files appear.
This core is different than the one submitted earlier today. i'm using
patch-299
_________________________________________________________________
http://liveearth.msn.com
_______________________________________________
Gluster-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
Anand V. Avati
_________________________________________________________________
Need a brain boost? Recharge with a stimulating game. Play now!
http://club.live.com/home.aspx?icid=club_hotmailtextlink1
_______________________________________________
Gluster-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/gluster-devel
