Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6x9J+69xkRtgZeQocW5Uo5uQs9dmoCgkqUHs0nYfPXmtw@mail.gmail.com>
Date: Wed, 13 Jun 2012 10:12:04 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: OS_TIMER and AMD SDK

On Wed, Jun 13, 2012 at 1:00 AM, magnum <john.magnum@...hmail.com> wrote:
> When using latest Ubuntu 12 with the distributions' AMD drivers, we get
> neither AMDAPPSDKROOT nor ATISTREAMSDKROOT from the environment so OS_TIMER
> does not get set to 0, and indeed we get the semaphore_wait problems.
>
> I have no idea how to fix this other than having all OpenCL builds set
> OS_TIMER=0.

For Ubuntu 12.x users, we can document that they need to set
AMDAPPSDKROOT or ATISTREAMSDKROOT variable correctly before attempting
to compile and run JtR. This should solve the problem.

-- 
Cheers,
Dhiru

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.