Re: [GNU Crypto] Suggestions for README build instructions (Test results)

[Raif S. Naffah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello Mark,

On Friday 11 October 2002 03:14, Mark Wielaard wrote:
> Hi,
>
> On Thu, 2002-10-10 at 18:31, Mark Wielaard wrote:
> > The generated test vectors seem to be the same (not all have been
> > generated yet) as the onces from:
> > ftp://ftp.gnupg.org/gcrypt/gnu-crypto/gnu-crypto-1.0.0-tv.tar.bz2
> > (Except that those are in 'ASCI with CRLF line terminators'
> > format.)

yup --they were re-directed, using cygwin on a windoors box.  the next 
ones won't be!


> The tests have finished and all test vectors are the same.
> I have attached the rest of the output.
> This is with a recent gnu.crypto and gcj from CVS
> [gcj (GCC) 3.3 20021009 (experimental)]
> On a i686-pc-linux-gnu machine.
> [AMD Athlon XP 1600+]
> And without the -O2 flag as stated earlier.

thanks muchly for all that work :-)

i'll try to digest and integrate it in my current attempt to normalise 
the build process (with GNU tools) of the library.  the new setup will 
use the "auto* dance" (as you call it :-) and will replace all 
make-related files at the toplevel as well as the gcj directory.  
options in the configure script will allow one to select which compiler 
to use (gcj, jikes or javac), and if/when it's GCJ, the shared library 
will get built.

i'll keep you and the list posted + cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE9pqkd+e1AKnsTRiERA5EFAJkBgffNJUfOlrdj9wQfo6RRWgC+NwCeOvaZ
vYaOKO6TV1bvsOaimOaNwiE=
=MxLh
-----END PGP SIGNATURE-----