Bernard Li wrote: > Hi Matt: > > On 12/10/07, Matthew Chambers <[EMAIL PROTECTED]> wrote: > > >> Thanks for the help. I tried that method, and got pretty far, but then >> got this error: >> >> gcc -O0 -I../lib -I../gmond -I../srclib/expat/lib/ -O3 -Wall >> -D_REENTRANT -O3 -o gmetad gmetad.o cmdline.o data_thread.o server.o >> process_xml.o rrd_helpers.o conf.o type_hash.o xml_hash.o cleanup.o >> -L/frogstar/usr/ppc/lib -L/usr/lib ../lib/.libs/libganglia.a >> /frogstar/usr/ppc/lib/librrd.a -L/lib -lpng12 -lpangocairo-1.0 >> -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm >> ../srclib/expat/lib/.libs/libexpat.a -ldl -lresolv -lnsl -lpthread >> /usr/bin/ld: cannot find -lpangocairo-1.0 >> collect2: ld returned 1 exit status >> >> I installed cairo-devel and pango-devel packages and the next build >> attempt worked fine, so it appears those dependencies are not properly >> checked for in the build (FYI). After that things went smoothly and it >> appears to be running fine (http://fenchurch.mc.vanderbilt.edu/ganglia); >> I only updated ganglia on the head node (hosting both the web frontend >> and gmetad). >> > > I am not sure why you are linking against pangocairo -- are you using > rrdtool 1.3 beta? The only time I saw the pangocairo dependency was > when I was fiddling around with the beta. Unless this is specific to > the ppc arch... > That's quite likely since rrdtool 1.3 did switch rendering from libpng to cairo. I think I've installed the 1.3 beta at one point, but /usr/bin/rrdtool is 1.2.23. Maybe that library in my /frogstar/usr/ppc/lib path is from a derelict 1.3 build, I can't remember and I don't know how to check. :P
> BTW, will you have time to implement the "click graph to enlarge" > feature that was introduced in 3.0.5 but not present in trunk? I > believe you were going to write some code once rrdtool 1.3 is released > to support that. > I didn't realize this was still a looked-for feature since I figured the front-end-related stuff on the 3.1 wish list would supersede such a feature? If there is a front-end logic overhaul, I expect it to allow for specifying graph sizes in pixels, so a click-to-enlarge feature would be trivial to implement. I don't think I have the time to commit to actually doing that overhaul, but I'm certain that my work on --full-size-mode in rrdtool 1.3 will prevent the front-end logic from needing any painful and hackish graph size calculations, though. :) To reiterate for this mailing list, the new rrdtool has an option to specify the final output image size in pixels (the default effect of changing the graph size changes the size of the "graph canvas" which is where the data is drawn). -Matt ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
