Re: [Ganglia-developers] Problem with the 2.5.8 build?

[Matt Massie]

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 {} \;

and found no reference in any file in the distribution.

when i ran

% find . -exec grep -l shared_ext {} \;
./aclocal.m4
./configure
./libtool

i found three files with the reference.





i'm sure we'll find out what's going on but i need more info.

has anyone else out there in ganglialand tried 2.5.8?

-matt

ps i will unicast-enable gmetric today or tomorrow.



Stu Teasdale wrote:

i don't think we're dealing with an autoconf/automake in compatibility here. you don't even need autoconf/automake/libtool etc installed on a machine to configure and make the distribution... all you need to "/bin/sh". can you please confirm the location of the sharext_cmds reference you're talking about? can you also confirm the md5 signature of the 2.5.8 tarball that you are using? can you please tell me your exact "./configure" commandline? can you please give me the exact error string that you find when you try to compile the unmodified distribution on your host?

On Fri, Nov 12, 2004 at 10:11:42PM +0000, Matt Massie wrote:

Stu Teasdale wrote:

Hi there,



Am I just being dumb or is there a problem?

Stu

I'm just trying out 2.5.8 and hit some build problems. The libraries in lib/.libs were being created without .so in their name. It appears that libtool now uses a variable to determine the extension for libraries, setting shrext_cmds, but then using shared_ext further down the script.

i'm curious... did you use the tarball distribution at
http://matt-massie.com/ganglia/ganglia-monitor-core-2.5.8.tar.gz
?

or did you bootstrap a local copy with
what platform did you try it on?

what happens if you do a

% make distclean
% ./configure
% make

??

i just ran a teest on fedora 2 and it configured and ran just fine. i'm sure you're not dumb. we'll figure it out.

Stu

This is debian "Sarge". Starting from a clean tarball shows the same behaviour, but changing references to sharext_cmds to shared_ext in the config.h.in, running autoconf and using the new configure script seems to build the shared objects with the correct extension. This could be come odd autoconf/automake version clash? The default debian autoconf is 2.59.

--
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

signature.asc
Description: OpenPGP digital signature