stu-

great feedback. i'm pretty sure that i tracked down the problem and fixed it. i confirmed that on my sarge box that a "make install" didn't correctly install libganglia.so (as ugly as it is).

i realized the problem was with libtool and in particular the ./config/ltmain.sh file being much too old.

i flushed the ./config directory and replaced the scripts with new scripts .. bootstrapped the code and made a new 2.5.8 distribution file which does install shared libraries correctly.

you can get it from
http://matt-massie.com/ganglia/ganglia-monitor-core-2.5.8.tar.gz
md5sum = 55913115d23e6b82adb1a4b265648d4e

let me know what you find and thanks for taking the time to provide good feedback.

-matt

Stu Teasdale wrote:
On Mon, Nov 15, 2004 at 11:28:41AM +0000, Matt Massie wrote:

i just downloaded the tarball on a 3.1 debian "sarge" box and it compiled just fine.

i downloaded the version at...
http://matt-massie.com/ganglia/ganglia-monitor-core-2.5.8.tar.gz
md5sum = b7f31c3ae2f4f91116f5c2c943a74458

and then ran

% find . -exec grep -l sharext_cmds {} \;


My mistake, the variable is shrext_cmds. While I pulled the tarball from the sourceforge site the md5sum matches. After doing a build typing you get:
yau:~/tmp/ganglia-monitor-core-2.5.8# ls lib/.libs
libganglia    libganglia.1.1.0  libganglia.la
libganglia.1  libganglia.a      libganglia.lai

No .so extensions to be seen, and this remains after install. This doesn't of course directly affect the compilation of gmond or gmetad themselves, as these use the .a file, but breaks shared library support, and causes problems with my attempts to build myself some update .deb packages following the template of the 2.5.5 packages in sarge atm.

Stu

--
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'

   They that can give up essential liberty to obtain a little
      temporary safety deserve neither liberty nor safety.
  --Benjamin Franklin, Historical Review of Pennsylvania, 1759

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to