Open GL errors after install of gr-fosphor

[aneitzel (André)]

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 appears without FFT and will closing. In Terminal i see this error:

###################################################################
imac:~ admin$ osmocom_fft -F
Mac OS; Clang version 7.0.2 (clang-700.1.81); Boost_105900; UHD_003.009.001-MacPorts-Release

gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.8.1
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy 
Number of USB devices: 7
USB device 1d50:6089: 000000000000000014d463dc2f391ee1 match
Using HackRF One with firmware 2015.07.2 
[!] gl_cmap shader compile log :
ERROR: 0:32: '' :  version '130' is not supported

[!] 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:32: '' :  version '130' is not supported

[!] gl_cmap shader compilation failed (cmap_bicubic.glsl)
[w] Color map shader 'bicubic' failed to load, will use fallback
[+] Selected device: GeForce GTX 780M
Segmentation fault: 11
###################################################################

I use a imac i7 3,4Ghz with 32GB RAM and 4GB Nvidia GTX 780. OS = El Captain. Osmocom-fft and other HackRF stuff running fine. Any hints? I thougt my imac should capable of OpenGL flawless...

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers gr-fosphor), if any.

Note that a "request" ticket type is only for requesting a new port and the Milestone field is for use by Macports team members only, please do not set it.

[michaelld (Michael Dickens)]

I see the same issue on my laptop (2012 MBPR). I've contacted the developer & he's looking into the issue. He's also quite busy. To the best of my debugging, this is not something I can fix; it's an upstream issue. Hopefully it'll get fixed sooner rather than later, but I can't say for certain when it will be. So, please be patient.

[246tnt@…]

The "gl_cmap shader compilation failed" errors are "normal" for OSX. They won't go away any time soon unless Apple decides to do like everyone else and support GLSL 1.3+ even for OpenGL 2.x contexts ...

But those should have little to no visual impacts. That certainly doesn't explain why you don't see anything or why you have a segmentation fault ...

[michaelld (Michael Dickens)]

Attaching a crashlog.

[michaelld (Michael Dickens)]

The osmocom crash log uses Wx, while mine uses Qt. Same basic issue. No ideas here.

[aneitzel (André)]

Replying to michaelld@…:

The osmocom crash log uses Wx, while mine uses Qt. Same basic issue. No ideas here.

How to choose between Wx or QT?

[aneitzel (André)]

I use latest OSX "El Captain" 10.11.2. and found out, that a make of "gr-fosphor" from OSMOCOM GIT repository also fail with:

imac:build admin$ cmake ../ -- The CXX compiler identification is AppleClang 7.0.2.7000181 -- The C compiler identification is AppleClang 7.0.2.7000181 -- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Build type not specified: defaulting to release. -- Found Git: /usr/bin/git (found version "2.5.4 (Apple Git-61)") -- Extracting version information from git describe... -- Boost version: 1.59.0 -- Found the following Boost libraries: -- system -- thread -- Found OpenGL: /System/Library/Frameworks/OpenGL.framework -- Found OpenCL: /System/Library/Frameworks/OpenCL.framework (found version "1.2") -- Found PkgConfig: /opt/local/bin/pkg-config (found version "0.28") -- Checking for module 'freetype2' -- Found freetype2, version 18.2.12 CMake Error at CMakeLists.txt:109 (message):

freetype2 required to compile gr-fosphor

Freetype is located in /opt/local/include/freetype2/ ??? Im confused because System says its found, list path and next step error thats not found?

Any hints?

[aneitzel (André)]

Good News: Seg Fault is SOLVED by installing latest NVIDIA Wedrivers on EL Captain: ​http://www.nvidia.com/download/driverResults.aspx/96651/en-us

After that osmocom_fft -F with start FOSPHOR without issues. Ticket can be closed since it was a driver issue on OS.

[michaelld (Michael Dickens)]

Updated drivers for some Macs: ​http://www.nvidia.com/download/driverResults.aspx/100824/en-us

[michaelld (Michael Dickens)]

I'm going to go ahead and close this ticket as "wontfix" (should be "cantfix") because it's not a MacPorts issue (as you wrote). Thanks for the info!

[michaelld (Michael Dickens)]

Good news: This issue is fixed in 10.12 Sierra! I'm not generally a proponent of updating to the ".0" release, but in this case I'm finding nothing outstandingly wrong with 10.12.0 ... so, maybe it's worth the update ... Being a developer I like to make sure the latest (beta) works well enough, and having fosphor running again is awesome!