[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae2c0609-8644-c54c-5650-82e2a2e44d68@mathiesen.info>
Date: Thu, 8 Jun 2017 12:54:47 +0200
From: Bjarne D Mathiesen <s022518@...hiesen.info>
To: john-users@...ts.openwall.com
Subject: Re: fatal error: 'opencl_device_info.h' file not found
magnum wrote:
> On 2017-06-08 01:53, Bjarne D Mathiesen wrote:
>> MacPro:src root# ../run/john -test -form:opencl
>> Device 1: ATI Radeon HD 5770
>> Build log: <program source>:42:10: fatal error: 'opencl_device_info.h'
>> file not found
>> #include "opencl_device_info.h"
>> ^
>
> Is that file present if you eg. "ls -l ../run/kernels/*.h" ? It should
> be.
It's there ; 1st thing I checked ;-)
MacPro:src root# ls -l ../run/kernels/*.h
-rw------- 1 bjarne staff 77 May 16 2014
../run/kernels/opencl_DES_WGS.h
-rw------- 1 bjarne staff 4623 May 16 2014
../run/kernels/opencl_DES_bs.h
-rw------- 1 bjarne staff 2710 Dec 18 2014
../run/kernels/opencl_bf_std.h
-rw------- 1 bjarne staff 2696 Oct 3 2014
../run/kernels/opencl_cryptsha256.h
-rw------- 1 bjarne staff 2897 Nov 11 2014
../run/kernels/opencl_cryptsha512.h
-rw------- 1 bjarne staff 2435 Oct 3 2014
../run/kernels/opencl_device_info.h
-rw------- 1 bjarne staff 256 May 20 2014
../run/kernels/opencl_lotus5_fmt.h
-rw------- 1 bjarne staff 4044 Dec 18 2014 ../run/kernels/opencl_md4.h
-rw------- 1 bjarne staff 5330 Dec 18 2014 ../run/kernels/opencl_md5.h
-rw------- 1 bjarne staff 5809 Dec 18 2014
../run/kernels/opencl_misc.h
-rw------- 1 bjarne staff 102924 May 16 2014
../run/kernels/opencl_nonstd.h
-rw------- 1 bjarne staff 1073 Nov 11 2014
../run/kernels/opencl_pbkdf1_hmac_sha1.h
-rw------- 1 bjarne staff 1073 May 16 2014
../run/kernels/opencl_pbkdf2_hmac_sha1.h
-rw------- 1 bjarne staff 1688 Sep 19 2014
../run/kernels/opencl_rawsha256.h
-rw------- 1 bjarne staff 1915 Sep 19 2014
../run/kernels/opencl_rawsha512.h
-rw------- 1 bjarne staff 5167 Dec 18 2014 ../run/kernels/opencl_rc4.h
-rw------- 1 bjarne staff 48025 May 16 2014
../run/kernels/opencl_sboxes-s.h
-rw------- 1 bjarne staff 54 May 16 2014
../run/kernels/opencl_sboxes.h
-rw------- 1 bjarne staff 7861 Dec 18 2014
../run/kernels/opencl_sha1.h
-rw------- 1 bjarne staff 32415 Dec 18 2014
../run/kernels/opencl_sha2.h
-rw------- 1 bjarne staff 4220 Oct 3 2014
../run/kernels/opencl_sha256.h
-rw------- 1 bjarne staff 22505 Oct 3 2014
../run/kernels/opencl_sha2_common.h
-rw------- 1 bjarne staff 9517 Oct 3 2014
../run/kernels/opencl_sha512.h
-rw------- 1 bjarne staff 15545 Dec 18 2014
../run/kernels/opencl_unicode.h
>> MacPro:src root# system_profiler SPSoftwareDataType
>> Software:
>> System Software Overview:
>> System Version: macOS 10.12.5 (16F73)
>> Kernel Version: Darwin 16.6.0
>>
>> I've been trying to solve this problem for several hours now.
>>
>> I've found the following :
>> http://www.openwall.com/lists/john-users/2014/08/03/2
>> but how do I execute the work-around
>
> You seem to be running latest OSX so that problem should not apply to
> you. Not sure what is wrong here. Are you using a recent Jumbo?
411 ./configure --enable-mpi LDFLAGS=-L/macports/lib
CFLAGS="-O2 -I/macports/include"
412 make clean && make -j6
MacPro:src root# ../run/john --list=build-info
Version: 1.8.0-jumbo-1 MPI
Build: darwin16.6.0 64-bit SSE4.1-autoconf
Arch: 64-bit LE
$JOHN is ../run/
Format interface version: 12
Max. number of reported tunable costs: 3
Rec file version: REC4
Charset file version: CHR3
CHARSET_MIN: 1 (0x01)
CHARSET_MAX: 255 (0xff)
CHARSET_LENGTH: 24
Max. Markov mode level: 400
Max. Markov mode password length: 30
Compiler version: 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)
gcc version: 4.2.1
clang version: 8.1.0 (clang-802.0.42)
OpenCL library version: 1.2
OpenSSL library version: 0100020cf
OpenSSL 1.0.2l 25 May 2017
GMP library version: 6.1.2
fseek(): fseek
ftell(): ftell
fopen(): fopen
memmem(): System's
>
> magnum
--
Bjarne Mathiesen mailto:s022518@...dent.dtu.dk
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.
