john-dev - cuda/rawsha256.o and make -j

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20120403223058.GA18474@openwall.com>
Date: Wed, 4 Apr 2012 02:30:58 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: cuda/rawsha256.o and make -j

Lukas -

I noticed that sometimes my "make -j8" builds would fail, and I've just
bothered to find out why.  Apparently, it happens when the below two
targets are built in parallel.  This is easily triggered when
cuda_rawsha256.h or cuda/rawsha256.cu have just been edited in an
otherwise already-built tree, but it sometimes happens in other cases as
well.  Can you correct this, please?

cuda_rawsha256.o:  cuda_rawsha256.h cuda/rawsha256.cu cuda_common.o
	cd cuda; nvcc $(NVCC_FLAGS) -DSHA256 rawsha256.cu
	mv cuda/rawsha256.o cuda_rawsha256.o

cuda_rawsha224.o:  cuda_rawsha256.h cuda/rawsha256.cu cuda_common.o
	cd cuda; nvcc $(NVCC_FLAGS) -DSHA224 rawsha256.cu
	mv cuda/rawsha256.o cuda_rawsha224.o

While you're at it, please also add the proper copyright and license
statements to cuda_rawsha256.h and cuda/rawsha256.cu.

Thanks,

Alexander

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.