On Fri, 2012-07-27 at 14:53 +0200, Tomasz Rybak wrote: […] > Is there any way I could make it more obvious to PyOpenCL users? > There is not many places I can put information about important > changes in package besides README.Debian and NEWS.
Sadly, I suspect there is not. As a person new to this, I just installed using aptitude those packages that seems most appropriate, and in an NVIDIA card situation nvidia-libopencl1 seems the most specific. As with most people, reading the README files in the documentation is the last thing one thinks of doing. I think the best way of avoiding hassle is to find some way of getting a link to the file high up the first page of a Google search for nvidia-libopencl1 1.2 (or some such query) > OpenCL (and PyOpenCL) is still young and there are quite > radical changes, especially with regards to management > of ICDs, free software, etc. Lenny does not contain any > OpenCL libraries, Squeeze contains only one OpenCL > implementation (NVIDIA one), Wheezy contains > 2 ICDs (AMD and NVIDIA) and 3 libopencl1 libraries > (AMD, NVIDIA, and free ocl-icd). It looks like > Wheezy+1 will have at least one free ICD. > Having many OpenCL implementations, including free ones, > is good situation, but at the same time might cause > some problems like those you have experienced. > At the same time I do not want to force users to > install only one OpenCL implementation to use with > PyOpenCL - this would be against spirit of free software, > could cause problems if/when new OpenCL implementation > is uploaded to Debian, would disallow experimentation and so on. Being an Unstable sort of person I tend to be Sid oriented (with a bit of Experimental thrown in) :-) […] > Without seeing kernel and PyOpenCL code calling it I cannot be sure, > but it looks like your code is passing some integer argument > while OpenCL kernel expects buffer. PyOpenCL checks if kernel > receives proper buffer and raises exception (which you got) > if not. > > This looks like error unrelated to PyOpenCL packaging - consider > asking more detailed questions on PyOpenCL mailing list: > http://lists.tiker.net/listinfo/pyopencl Indeed. I think your thoughts are well on track to indicating the problem, but it is not Debian package related so I will definitely take the problem to a more appropriate place. Thanks. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
