Date: Sat, 22 Aug 2020 19:54:49 +0200 From: Solar Designer <solar@...nwall.com> To: john-users@...ts.openwall.com Subject: Re: OpenCl lib not detected On Sat, Aug 22, 2020 at 09:28:06AM -0800, Royce Williams wrote: > On Sat, Aug 22, 2020 at 5:06 AM Solar Designer <solar@...nwall.com> wrote: > > On Sat, Aug 22, 2020 at 12:13:07PM +0000, freeroute wrote: > > > > I think the autoconf did not find the OpenCL lib. > > > > It looks so. Per the full configure output, it looks like the OpenCL > > headers you have in /usr/include/CL are working OK. > > > > As an alternative to passing explicit LDFLAGS, you could ensure the > > library path is specified somewhere under /etc/ld.so.conf.d, and run > > "ldconfig" to ensure the paths specified in there are in effect. > > If this explains why some people have this symptom and others don't ... is > this something that would normally be automatically triggered by the OpenCL > install? Or is this something that everyone should be aware of, or should > be mentioned in README-OPENCL, and/or some part of the ./configure output, > etc.? It feels as though this should be more discoverable (using a variety > of methods/channels). When a libOpenCL is installed by any package or any driver's or toolkit's installer, I'd expect its directory path (if it's not a standard library directory for the system) to be automatically added to /etc/ld.so.conf.d/, and (regardless of whether the directory is a standard one or not) "ldconfig" to be invoked (like any package installing a library normally does). I don't know why this might not have happened in freeroute's case; or maybe it did happen, and the problem was different. 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.