Cheshire Cat Computing

Re: 64 bit compilation issue

2009-01-19T12:20:57+13:00

You'll definitely need to recompile the mcrypt library (open source) for 64bit. http://sourceforge.net/project/showfile ... p_id=87941

Then make sure you're linking against the mcrypt library, and also the socket library - that should get rid of most of these messages.

Finally, the WSA* errors are Winsock functions - possibly there is a winsock library, or else these are included in the socket library. Otherwise it sounds like things have compiled and the problem is now only at linking stage.

Statistics: Posted by stevesh — Mon Jan 19, 2009 12:20 pm

Re: 64 bit compilation issue

2008-10-15T10:20:57+13:00

I think you'll need to recompile the mcrypt library in 64bit, that should get rid of the mcrypt-related problems. mcrypt is open source (its how I compiled it) so that should be OK - but I suspect I didnt ship the source for mcrypt with the package?

The linking erros with WSA and __imp_* seem to be related to the Winsock2 library function calls. Maybe they need to be defined differently under 64bit? I'll need to check to find out where they are defined in the code.

Statistics: Posted by stevesh — Wed Oct 15, 2008 10:20 am

Re: 64 bit compilation issue

2008-10-14T20:18:44+13:00

Statistics: Posted by staylor — Tue Oct 14, 2008 8:18 pm

Re: 64 bit compilation issue

2008-10-14T10:22:32+13:00

Statistics: Posted by stevesh — Tue Oct 14, 2008 10:22 am

64 bit compilation issue

2008-10-14T04:36:56+13:00

Statistics: Posted by staylor — Tue Oct 14, 2008 4:36 am