Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 16 Sep 2014 13:51:03 -0400
From: David <>
Subject: Re: EC2 g2.2xlarge

Got it!  Here’s what I ended up doing to get it going:

ln -s /opt/nvidia/cuda /usr/local/cuda
ln -s /opt/nvidia/cuda/include/CL /usr/local/include/CL

After that, configure was happy (CUDA and OpenCL enabled).

Make still failed with the error below, but re-running configure like this fixed that (thank you google):

./configure LDFLAGS="-L/usr/lib64/ -lstdc++"

The make completes successfully now, john wouldn’t run:

./john:  error while loading shared libraries: cannot open shared object file: No such file or directory

To fix that:

echo “/usr/local/lib” > /etc/

Now john runs and tests fine.  Now I’m curious to see how it actually performs…

On Sep 15, 2014, at 19:25 , magnum <> wrote:

> On 2014-09-15 22:26, David wrote:
>> I apologize in advance as I’m kind of stabbing in the dark, but looking a little closer today, here is what I get:
>> $ ./configure NVIDIA_CUDA=/opt/nvidia/cuda/
>> Looking through the configure output it looks like it also doesn’t know where to find cl.h, which in this case lives at /opt/nvidia/cuda/include/CL/
> Off the top of my head you do it just right. Not sure what ends up wrong. After running configure, you could verify/edit the generated Makefile. With your invocation it should already contain "-I/opt/nvidia/cuda/include" and that should be enough.
>> How do I tell the configure script (or edit the Makefile) so it knows where to find cl.h?  I’m guessing I also need to tell it somehow to look in /usr/lib64/ for the file mentioned below?
>>> /usr/bin/ar: creating aes.a
>>> /usr/bin/ld: cuda_common.o: undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3'
>>> /usr/bin/ld: note: '__gxx_personality_v0@@CXXABI_1.3' is defined in DSO /usr/lib64/ so try adding it to the linker command line
>>> /usr/lib64/ could not read symbols: Invalid operation
>>> collect2: error: ld returned 1 exit status
>>> make[1]: *** [../run/john] Error 1
>>> make: *** [default] Error 2
> I believe it does find but doesn't quite like it? Sorry, I have no idea.
> 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.