On 14-Aug-07, at 1:40 PM, Christian Biere wrote: >> The following occurred upon startup with a clean build using prior >> configuration defaults. > > Could you tell in terms of commands what this means?
This means starting from scratch, with the prior config file defaults. I still use "./Configure.sh" rather than "./build.sh" for some reason (because of the library extensions if I recall correctly, but I'm not sure), but the same stage. Then "make define." Then "make." Then "make install." This was necessary anyways because of the addition of the new directory for the shell commands. Normally, I've been starting with make clean whenever major changes have happened, but there's not much time lost by scripting in the configuration; it's only a fraction of the make time. So I'll do that in the future, for sure. Whatever it was, yes, it's gone now. Asta la vista, buggy. - 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
