[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00b601d22fd3$f8d613f0$ea823bd0$@net>
Date: Wed, 26 Oct 2016 17:57:40 -0400
From: "Robert Harris" <rs904c@...scape.net>
To: <john-users@...ts.openwall.com>
Subject: RE: JtR -test error 2016-10-25 in Cygwin x64
Actually I didn't have the parens in there during build time, I renamed it later. Then I attempted to run the tests. I'll go re-test with those parens.
-----Original Message-----
From: magnum [mailto:john.magnum@...hmail.com]
Sent: Tuesday, October 25, 2016 6:50 PM
To: john-users@...ts.openwall.com
Subject: Re: [john-users] JtR -test error 2016-10-25 in Cygwin x64
On 2016-10-25 22:52, Robert Harris wrote:
> I built John in Cygwin x64 bit and received an error during the
> built-in test.
>
> Someone up for fixing this?
> Options used: -I
> "/cygdrive/u/JtR/JohnTheRipper-bleeding-jumbo-2016-10-16(compiled
> without pcap support)/run/kernels" -cl-mad-enable -DDEVICE_INFO=64
> -DSIZEOF_SIZE_T=8
> -DDEV_VER_MAJOR=0 -DDEV_VER_MINOR=13 -D_OPENCL_COMPILER
> -DHASH_LOOPS=1024
> -DOUTLEN=20 -DPLAINTEXT_LENGTH=64 -DV_WIDTH=4
> $JOHN/kernels/pbkdf1_hmac_sha1_kernel.cl
>
> Build log: Invalid build option: without
So you have parens and spaces in your path, and the fact we use quotes around it doesn't help (with this OpenCL runtime). I know Atom has struggled with this issue too, in Hashcat. There doesn't seem to be a fully portable way to handle this. I believe Atom's current best-effort solution is to chdir to that directory before building instead of trying to use the non-portable -I option. I'm not sure I like to do the same.
The quick and easy solution is to avoid problematic characters in paths.
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.
