Am 04.03.2015 um 11:49 schrieb Germano Massullo: > Ulrich, ping :-) >
Obviously the driver is not only nonfunctional for the hardware but contains a bug which triggers a SIGABRT. Nothing we can do here as long as this doesn't get fixed in the driver code. Only option is to run darktable with --disable-opencl as suggested in the manual. Does the driver need to be shipped with debugging enabled? With debugging disabled at least the assert statement will not cause the driver to terminate. Ulrich -- *Ulrich Pegelow* · Benrodestraße 76 · 40597 Düsseldorf ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
