Thread: Re: [Mcrypt-developers] List Still Alive?

Yip, the list is still alive. Sometime I wonder if I
am, the way work is going right now. :) I'm going to
get some more work done on MCrypt done this weekend -
I hope! If all goes well, a new release should be out
soon.

MHash has been slightly more active, because I've been
getting a lot of patches for that. However, MCrypt has
not been forgotten.

--- Tod Thomas <tt...@ch...> wrote:
> Just checking.
> 
> 
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Mcrypt-developers mailing list
> Mcr...@li...
>
https://lists.sourceforge.net/lists/listinfo/mcrypt-developers
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Jonathan Day wrote:
> Yip, the list is still alive. Sometime I wonder if I
> am, the way work is going right now. :) I'm going to
> get some more work done on MCrypt done this weekend -
> I hope! If all goes well, a new release should be out
> soon.
> 
> MHash has been slightly more active, because I've been
> getting a lot of patches for that. However, MCrypt has
> not been forgotten.

Ok, great.  Thanks for getting back to me.

Tod

I've been having problems building on Solaris, so I started over from 
scratch this morning.  I started with a fresh v2.5.7 tarball on a 
Solaris 8 machine.

After running a vanilla ./configure followed by make I got typical make 
feedback.  Then I got this (truncated for brevity):

...
gost_LTX__mcrypt_self_test          ../lib/.libs/libmcrypt.so
gost_LTX__mcrypt_algorithm_version  ../lib/.libs/libmcrypt.so
ecb_LTX__mcrypt_get_state           ../lib/.libs/libmcrypt.so
ecb_LTX__mcrypt_set_state           ../lib/.libs/libmcrypt.so
tripledes_LTX__mcrypt_self_test     ../lib/.libs/libmcrypt.so
ld: fatal: Symbol referencing errors. No output written to .libs/ciphertest
collect2: ld returned 1 exit status
make[2]: *** [ciphertest] Error 1
make[2]: Leaving directory `/export/home/ldap/work/libmcrypt-2.5.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/export/home/ldap/work/libmcrypt-2.5.7'
make: *** [all] Error 2

So I did a make clean to try again.  Once again I ran make.  This time 
it completes successfully!

So I try make check, and I get this output:

Making check in src
make[1]: Entering directory `./work/libmcrypt-2.5.7/src'
make  check-TESTS
make[2]: Entering directory `./work/libmcrypt-2.5.7/src'
Error getting algorithms/modes
FAIL: ciphertest
Failed to initialize cipher - rijndael-128/cfb
FAIL: aestest
===================
2 of 2 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/export/home/ldap/work/libmcrypt-2.5.7/src'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/export/home/ldap/work/libmcrypt-2.5.7/src'
make: *** [check-recursive] Error 1


So I changed into the src directory and tried running ./ciphertest and 
./aestest manually.

./ciphertest produces:  Error getting algorithms/modes
./aestest displays: Failed to initialize cipher - rijndael-128/cfb

Incidentally I got this to work without a problem on a RH8 box.  Does 
anybody have any idea what the problem could be?


Thanks - Tod



gcc V3.4.1
libtool V1.5.14
GNU ld version 2.11.2