|
From: | Matthias W. Klein |
Subject: | Re: New Octave package "OCL" providing OpenCL support |
Date: | Sat, 25 May 2019 16:51:59 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
>> I added a "Troubleshooting" section in OCL's README file... >> >> Can you try and comment? > > I would. But its not clear to me how to use this from source. There are two answers to that: 1.) All the steps from my troubleshooting list are commands on the octave command line, so you don't need to bother with sources. Since you obviously use an octave version which allows you to install the package release tarball, the distinguishing steps are ready at your hand - which is exactly what I intend for all users. 2.) You (as a developer) want to track down (or debug) actual causes of segfaults etc., relying on sources. You can work with sources and build using my Makefile. See my post to your Ticket https://sourceforge.net/p/octave-ocl/tickets/4/ . Sorry for the delay - I focussed on critical technical issues recently and just didn't find the time to answer. Matt On 25.05.2019 01:36, Colin Macdonald wrote:
On 2019-05-24 10:02 a.m., Matthias W. Klein wrote:I added a "Troubleshooting" section in OCL's README file, including a list of steps / commands to test, whenever OpenCL issues or segfaults appear. See the tip version of README: https://sourceforge.net/p/octave-ocl/code/ci/default/tree/README This description reflects some experience made, but can still be considered (advanced) work in progress. Can you try and comment?I would. But its not clear to me how to use this from source. A while ago I filed https://sourceforge.net/p/octave-ocl/tickets/4/ I assume I put all the .c and .h files in src/ and the .m files in inst/ ? Also, the number of developers on this list running 4.2 is probably shrinking. I can do it with mtmiller's docker images but currently not working on my system... Colin
[Prev in Thread] | Current Thread | [Next in Thread] |