New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'inc_vendor.cl' file not found on macOs High Sierra 10.13.6 (17G65) #1706
Comments
Why do you use naive-hashcat.sh ? a third-party tool not developed/supported/maintained by hashcat ? Please download the source code of the release version from https://hashcat.net/hashcat and extract it with "7z x". Enter the extracted folder and compile it according to the instructions (https://github.com/hashcat/hashcat/blob/master/BUILD.md), then run something like
(to benchmark the MD5 speed of your setup) My guess is that it has something to do with naive-hashcat.sh and is not really a hashcat problem. You could also make sure that the file OpenCL/inc_vendor.cl exists within the extracted folder (from the downloaded file from https://hashcat.net/hashcat) |
No response from OP and probably an error in a third party overlay, therefore closing issue. Feel free to reopen. |
Hi. I have the same problem. Install hashcat like this:
` Benchmarking uses hand-optimized kernel code by default. /hashcat/OpenCL/m02500-optimized.cl: Optimized kernel requested but not needed - falling back to pure kernel
Benchmark relevant options:
Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4095) clBuildProgram(): CL_BUILD_PROGRAM_FAILURE Error returned by cvms_element_build_from_source
Started: Sun Aug 11 17:01:33 2019 |
+1
|
Same here: ➜ hashcat git:(master) ./hashcat -b -m 0 Benchmarking uses hand-optimized kernel code by default. OpenCL API (OpenCL 1.2 (Sep 5 2019 21:59:08)) - Platform #1 [Apple]
Benchmark relevant options:
Hashmode: 0 - MD5 clBuildProgram(): CL_BUILD_PROGRAM_FAILURE :9:10: fatal error: 'inc_vendor.h' file not found
Started: Wed Dec 4 18:28:03 2019 Don't know what else to do... :c |
Any suggestions?
The text was updated successfully, but these errors were encountered: