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.
CVSROOT: /usr/local/cvs Module name: cvsnt Changes by: arthur.barrett at march-hare.com Wed Apr 23 07:05:00 2008 On host: acerW64lap.march-hare.local Directory: cvsnt/cvsapi M Makefile.am CVSNT_2_0_x 1.1.2.29 -> 1.1.2.30 Bug Id: Directory: cvsnt/cvsapi/ufc-crypt A COPYING CVSNT_2_0_x -> 1.1.2.1 Bug Id: A Makefile.in CVSNT_2_0_x -> 1.1.2.1 Bug Id: A README CVSNT_2_0_x -> 1.1.2.1 Bug Id: A S2o CVSNT_2_0_x -> 1.1.2.1 Bug Id: A cert.c CVSNT_2_0_x -> 1.1.2.1 Bug Id: A cert.data CVSNT_2_0_x -> 1.1.2.1 Bug Id: A crypt.c CVSNT_2_0_x -> 1.1.2.1 Bug Id: A crypt.s300.S CVSNT_2_0_x -> 1.1.2.1 Bug Id: A crypt.sparc.S CVSNT_2_0_x -> 1.1.2.1 Bug Id: A crypt.sun3.S CVSNT_2_0_x -> 1.1.2.1 Bug Id: A crypt_util.c CVSNT_2_0_x -> 1.1.2.1 Bug Id: A do_ranlib CVSNT_2_0_x -> 1.1.2.1 Bug Id: A patchlevel.h CVSNT_2_0_x -> 1.1.2.1 Bug Id: A speeds.c CVSNT_2_0_x -> 1.1.2.1 Bug Id: A ufc-crypt.h CVSNT_2_0_x -> 1.1.2.1 Bug Id: A ufc.c CVSNT_2_0_x -> 1.1.2.1 Bug Id: Log message: As noted in previous checkin comments, linking in the ufc-crypt library using the .a file appears to fail miserably (at least on HPUX) and linking in to ../ufc-crypt/ on debian linux gives libtool grief since it goes looking for .deps/../ufc-crypt/etc So this is a miserably hack to at least get it compiling. If it works I then propose going back and altering the .vcproj to 'point' to the files in cvsapi/ufc-crypt and leave the .vcproj itself in the orig location, probably would need to fix the Makefile in the root as well...