Hi, On 12/13/2013 12:01 AM, Gareth Owen wrote: > I think I know why this is - I've been doing some stuff with CUDA, so I > downloaded the nVidia CUDA toolkit package which also comes with OpenCL > development files - however these are 1.1 headers and libraries, so when clang > looks for opencl.h and links against -lOpenCL, it finds the nVidia files which > don't contain clCreateImage which comes with 1.2. > > Is there a way around this? I've been quite interested in pocl as the nVidia > support for OpenCL is somewhat lackluster...
This is a known problem, see: https://github.com/pocl/pocl/issues/27 It stems from the fact that -lOpenCL is assumed to be the ICD loader in the ICD build which the pocl test suite assumes to be version 1.2 and contain its symbols. pocl lacks a configure check for it at least. You can work around this by building and installing an ICD loader with 1.2 headers and ensuring the pocl build finds it first (e.g. via LDFLAGS). Also you can build without ICD support and link directly against libpocl.so. Or just ignore the test linkage errors (which require 1.2 symbols). I think the 1.2 libpocl.so should still work with an 1.1 ICD loader, just the 1.2 functions are not usable then. http://portablecl.org/docs/html/development.html#ocl-icd -- --Pekka ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
