[MacPorts] #43710: Open GL & CL errors after flawless install of gr-fosphor

[MacPorts]

#43710: Open GL & CL errors after flawless install of gr-fosphor
--------------------------+-------------------------
  Reporter:  xformdave@…  |      Owner:  michaelld@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.2.1
Resolution:               |   Keywords:  mavericks
      Port:  gr-fosphor   |
--------------------------+-------------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => michaelld@…


Old description:

> After a successful instal and launch of the normal osmosdr_fft when
> attempting to launch with the gr-fosphor graphics acceleration I receive
> errors and the python app window is blank.  Machine is a 13" macbook 8,1,
> 2.7 ghz dual core i7, 10.9.2.
>
> Errors as they came (each appeared several times during launch):
>
> 1st is probably unrelated but seen this several times will toying with
> gr-osmosdr and gqrx:
>
> 2014-05-13 20:27:08.820 Python[4980:d07] CoreText performance note:
> Client called CTFontCreateWithName() using name ".Lucida Grande UI" and
> got font with PostScript name ".LucidaGrandeUI". For best performance,
> only use PostScript names when calling this API.
>
> 2nd chuck Open GL related:
> [!] gl_cmap shader compile log :
> ERROR: 0:27: '' :  version '150' is not supported
> ERROR: 0:27: '' : syntax error #version
>
> [!] gl_cmap shader compilation failed (cmap_simple.glsl)
> [w] Color map shader 'simple' failed to load, will use fallback
> [!] gl_cmap shader compile log :
> ERROR: 0:27: '' :  version '150' is not supported
> ERROR: 0:27: '' : syntax error #version
>
> [!] gl_cmap shader compilation failed (cmap_bicubic.glsl)
> [w] Color map shader 'bicubic' failed to load, will use fallback
> [+] Selected device: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
>
> Last the CL error:
>
> [!] CL Error (-54,
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
> .org_release_tarballs_ports_science_gr-fosphor/gr-fosphor/work/gr-
> fosphor-20140112/lib/fosphor/cl.c:684): Unable to queue FFT kernel
> execution
>
> followed after 20+ reoccurrences by an error 11 seg fault.
>

> I am admittedly in slighlty over my head at this point but to have things
> mostly working only to fault at this last step of gr-fosphor is
> frustrating. Any input is appreciated.

New description:

 After a successful instal and launch of the normal osmosdr_fft when
 attempting to launch with the gr-fosphor graphics acceleration I receive
 errors and the python app window is blank.  Machine is a 13" macbook 8,1,
 2.7 ghz dual core i7, 10.9.2.

 Errors as they came (each appeared several times during launch):

 1st is probably unrelated but seen this several times will toying with gr-
 osmosdr and gqrx:

 {{{
 2014-05-13 20:27:08.820 Python[4980:d07] CoreText performance note: Client
 called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
 with PostScript name ".LucidaGrandeUI". For best performance, only use
 PostScript names when calling this API.
 }}}

 2nd chuck Open GL related:

 {{{
 [!] gl_cmap shader compile log :
 ERROR: 0:27: '' :  version '150' is not supported
 ERROR: 0:27: '' : syntax error #version

 [!] gl_cmap shader compilation failed (cmap_simple.glsl)
 [w] Color map shader 'simple' failed to load, will use fallback
 [!] gl_cmap shader compile log :
 ERROR: 0:27: '' :  version '150' is not supported
 ERROR: 0:27: '' : syntax error #version

 [!] gl_cmap shader compilation failed (cmap_bicubic.glsl)
 [w] Color map shader 'bicubic' failed to load, will use fallback
 [+] Selected device: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
 }}}

 Last the CL error:

 {{{
 [!] CL Error (-54,
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
 .org_release_tarballs_ports_science_gr-fosphor/gr-fosphor/work/gr-
 fosphor-20140112/lib/fosphor/cl.c:684): Unable to queue FFT kernel
 execution
 }}}

 followed after 20+ reoccurrences by an error 11 seg fault.


 I am admittedly in slighlty over my head at this point but to have things
 mostly working only to fault at this last step of gr-fosphor is
 frustrating. Any input is appreciated.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/43710#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X