Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
David, Compile discussions really do belong on cvsnt-dev - finding them in the cvsnt support list is difficult and it's a limited audience that is interested anyway. http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt-dev Or cvsnt-dev at cvsnt.org Or news://news.cvsnt.org/support.cvsnt-dev > FYI, the QA warnings were something raised by the gentoo ebuild > system... I finally applied the right voodoo in the ebuild to > fix this > problem. > > The main hiccup that I came across was with libxml2 (missing > makefile during make?)... I got around this by ensuring that > libxml2 2.7.2 was installed in the system instead of using > the libxml2 that came with cvsnt. > > BTW, I did try configure with '--with-internal-libxml' and it threw > the same error during make. You may want to read this: http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?tt=1&id= 5159 If the installed libxml2 version is 2.6.2x then it should be automatically used, otherwise the internal libxml2 is used. The only platforms where we currently use the internal libxml2 are RedHat, Mac OS and maybe Solaris 9 (on HPUX we've provided our own libxml2.sl for even CVSNT 2.5.03 - but I'm not really sure why). If the libxml2 makefile doesn't exist during make then it usually means that it has detected that there is a suitable libxml2 already installed - in this case I don't think --with-internal-libxml works. It is MUCH better to use an already installed library, for security patches alone... Regards, Arthur Barrett