Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53320563.5090607@securibox.net>
Date: Tue, 25 Mar 2014 23:38:27 +0100
From: "-.-PhanTom-.-" <phantom@...uribox.net>
To: john-users@...ts.openwall.com
Subject: Re: john-1.8.0-Win-32 - john.omp.exe - cores used

On 25-03-2014 23:09, Solar Designer wrote:
> They're not required to be in the same dir. We're merely adding them 
> into the same dir in the builds we distribute, because people might 
> not have Cygwin installed or it might not be a compatible version (and 
> also because our cygwin1.dll is patched, but that's a separate story). 
> When you do have Cygwin installed and are building programs, you're 
> indeed _not_ required to copy Cygwin DLL's for each and every program. 
> That would largely defeat the purpose of using dynamic linking. 

> As Jim explained, setting up environment variables may be part of 
> Cygwin setup, which you probably haven't completed. Doesn't Cygwin's 
> "launch bash" desktop icon setup the env vars, though? 
I did add the Cygwin path to the Windows enviroment variables, but still 
get the error message when trying to run john in a windows command prompt..

> Yes, it's weird. I suggest that you debug step by step: try making a 
> non-OpenMP 64-bit build first and measure its speeds. Also, look at 
> speeds you're getting for other hash types, for both builds.
Okay, I will try that tomorrow.
> BTW, why don't you enable AVX?  Use an -x86-64-avx make target.
This is only available under Linux, right?
I will install Ubuntu in VMWare tomorrow and check it out.


Regards
-.-PhanTom-.-

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.