[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4bf0e72323e2beddcc9fdffd683d2e8b@smtp.hushmail.com>
Date: Sat, 17 Oct 2015 20:01:53 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: opencl error
It's supposed to hold copies of src/opencl/* as well as (basically)
src/opencl_*.h. But that should happen when you build.
Does "make -s" output any warnings or errors?
magnum
On 2015-10-17 15:36, noir maru wrote:
> Hi.
>
> No the run/kernels directory is empty. Is there something I need to do to
> populate it?
>
> Thanks
>
> On Sat, Oct 17, 2015 at 3:29 PM, magnum <john.magnum@...hmail.com> wrote:
>
>> Does run/kernels contain a bunch of files ending in .cl or .h ?
>>
>> magnum
>>
>> On 2015-10-16 20:52, noir maru wrote:
>>
>>> Thanks for the reply. running it from src has the same result. any other
>>> ideas? thanks
>>>
>>> On Fri, Oct 16, 2015 at 10:58 PM, magnum <john.magnum@...hmail.com>
>>> wrote:
>>>
>>> On 2015-10-16 15:54, noir maru wrote:
>>>>
>>>> I am trying to use dmg-opencl
>>>>>
>>>>> I receive the following output with an error that isn't reported
>>>>> elsewhere.
>>>>> Can anyone help? I am using the jumbo from github built with configure
>>>>> and
>>>>> make on mavericks.
>>>>>
>>>>> ./john --test --format=dmg-opencl
>>>>>
>>>>> Will run 4 OpenMP threads
>>>>> Device 1: Radeon HD 4870
>>>>> Benchmarking: dmg-opencl, Apple DMG [PBKDF2-SHA1 OpenCL 3DES/AES]...
>>>>> (4xOMP) Can't read source kernel: No such file or directory
>>>>>
>>>>>
>>>> I recall Mavericks had some problems with search paths. Try cd'ing to the
>>>> src directory and run john as "../run/john --test --format=dmg-opencl".
>>>> Does this help? If it does, your kernel should now be cached and from now
>>>> on you can run that format from the run directory like you expected.
>>>>
>>>> magnum
>>>>
>>>>
>>>>
>>>
>>
>
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.
