Hey there, I'm just getting things running under Leopard. Apparently I should be really excited about D-trace, but I haven't had the time to learn about it yet. The first thing I've noticed is a odd glitch in the Configure script when it tests for usable versions of Glib and Gtk. The conditional expressions in the script at lines 7026 & 7101, for instance:
> if [ "$gtkversion" = 1 ] && [ gtk-config --cflags >/dev/null 2>&1 ]; > then Always fail, as the second term always evaluates as false. (The result, "sh: [: gtk-config: unary operator expected" is hidden). Changing the test to something like this: > if [ "$gtkversion" = 1 ]; then > if gtk-config --cflags >/dev/null 2>&1 ; then works just fine (with extra 'fi', of course). There's probably a much tidier way to do it. I also noticed a fair number of messages such as: > Checking to see if your C compiler knows about "volatile"... > rm: try.dSYM: is a directory which go away if all the 'rm -f' expressions are changed to 'rm -Rf'. Finally, gettext, glib & gtk1-1.2.10 appear to rely heavily on convenience environmental variables such as '$SED' and '$EGREP' being set to the corresponding binary. I never encountered this as a problem in Tiger (OS X 10.4). Are these assumed to be defined on one's system, or am I missing an element of the ltconfig and/or (gnu) libtool rigamarole? - Matt ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
