Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171026121239.GA17063@openwall.com>
Date: Thu, 26 Oct 2017 14:12:39 +0200
From: Solar Designer <solar@...nwall.com>
To: altr@...2.de
Cc: john-dev@...ts.openwall.com
Subject: Re: Linux x86_64

Hi,

On Thu, Oct 26, 2017 at 01:19:17PM +0200, altr@...2.de wrote:
> I am new to this mailinglist, because I compiled jtr on a few  
> platforms and ran into various problems.

Your message would be more appropriate for the john-users list than for
john-dev.  You're reporting a problem rather than intend to participate
in JtR development (as far as I can tell from your message).

> make clean && make
[...]
> make[1]: Entering directory 
> `/nfs__share/ae/cc/189/JohnTheRipper/src/escrypt'
> /bin/rm -f tests crypto_scrypt-best.o crypto_scrypt-common.o sha256.o  
> tests.o crypto_scrypt-*.o
> make[1]: Leaving directory `/nfs__share/ae/cc/189/JohnTheRipper/src/escrypt'
> make find_version
> make[1]: Entering directory `/nfs__share/ae/cc/189/JohnTheRipper/src'
> /bin/mkdir -p ../run/kernels
> cp ../run/kernels ../run/kernels
> cp: omitting directory `../run/kernels'
> make[1]: *** [opencl/7z_kernel.cl] Error 1

I can't reproduce the problem.  For me, this looks as follows:

make[1]: Entering directory `/home/solar/j/bleeding-jumbo-20171026/src/escrypt'
/bin/rm -f tests crypto_scrypt-best.o crypto_scrypt-common.o sha256.o tests.o crypto_scrypt-*.o
make[1]: Leaving directory `/home/solar/j/bleeding-jumbo-20171026/src/escrypt'
make find_version
make[1]: Entering directory `/home/solar/j/bleeding-jumbo-20171026/src'
/bin/mkdir -p ../run/kernels
cp opencl_device_info.h ../run/kernels
cp opencl_misc.h ../run/kernels

... and so on.

In your case, the "cp ../run/kernels ../run/kernels" command is clearly
wrong, but it is unclear why it became so wrong.

magnum, on a related note, maybe we should have configure suggest "-j"
in the second make, e.g. replace:

Configure finished.  Now 'make clean && make -s' to compile.

with:

Configure finished.  Now 'make clean && make -sj8' to compile.

given that almost everyone is on a multi-core machine these days.
Ideally, we'd determine and include the logical CPU count in there, but
even a generally reasonable constant like 8 would do.

Alexander

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.