gr-fosphor @20160522 build broken

[michael.kirkhart@…]

Some time ago while running a sudo port update - sudo port upgrade outdated operation, I found the latest version of gr-fosphor was broken. Today I ran another update - upgrade outdated operation, and it is still broken.

As instructed, I ran sudo port -d -y rev-upgrade, and captured the output. I also tried running sudo port clean, then sudo port install gr-fosphor, and it is still broken.

This could be viewed as a duplicate of ticket #51803, but in my case, I do not have brew installed; I am only using MacPorts. Based on what I saw in ticket #51803, I also ran the following commands and captured the output:

otool -L /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gnuradio/fosphor/_fosphor_swig.so 
otool -L /opt/local/lib/libgnuradio-fosphor.3.7.0git.dylib

I have attached a file containing the output captures from all of this. I hope this information will help resolve the problem.

[mf2k (Frank Schima)]

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

[michaelld (Michael Dickens)]

What does the following return:

port installed

[michael.kirkhart@…]

output from port installed

[michael.kirkhart@…]

I have attached the file created by the following:

port installed > MacPorts-installed.txt

[michaelld (Michael Dickens)]

Thanks. What does the following return:

uname -a
otool -L /opt/local/lib/libglfw.dylib

[michael.kirkhart@…]

Here is what I got from uname:

Michaels-MacBook-Pro:~ michael$ uname -a
Darwin Michaels-MacBook-Pro.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64

Here is what I got from otool:

Michaels-MacBook-Pro:~ michael$ otool -L /opt/local/lib/libglfw.dylib 
/opt/local/lib/libglfw.dylib:
	lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 22.0.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1258.1.0)
	/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.5.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
	/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1404.46.0)
	/System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 600.0.0)
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 728.9.0)
	/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1258.0.0)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

[michaelld (Michael Dickens)]

OK; interesting. I'm also running 10.11 El Capitan & I don't see this issue. Strange.

Can you do the following:

sudo port destroot glfw
gzip -c $(port logfile glfw) > ~/Desktop/glfw_log.txt.gz

and then post the compressed log file to this ticket.

[michael.kirkhart@…]

Output from gzip -c $(port logfile glfw)

[michael.kirkhart@…]

Sure.

Not sure if you care, but this was the output from:

sudo port destroot glfw

Michaels-MacBook-Pro:~ michael$ sudo port destroot glfw
Password:
--->  Computing dependencies for glfw
--->  Fetching distfiles for glfw
--->  Attempting to fetch glfw-3.2.tar.gz from https://distfiles.macports.org/glfw
--->  Verifying checksums for glfw                                              
--->  Extracting glfw
--->  Applying patches to glfw
--->  Configuring glfw
--->  Building glfw
--->  Staging glfw into destroot

I have attached the requested output from:

gzip -c $(port logfile glfw)

Hope this sheds some light on the situation.

[michaelld (Michael Dickens)]

Great. What does the following return:

otool -L  $(port work glfw)/destroot/opt/local/lib/libglfw.dylib

[michael.kirkhart@…]

Here is the output from otool:

Michaels-MacBook-Pro:~ michael$ otool -L  $(port work glfw)/destroot/opt/local/lib/libglfw.dylib
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_glfw/glfw/work/destroot/opt/local/lib/libglfw.dylib:
	/opt/local/lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 22.0.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1258.1.0)
	/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.5.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
	/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1404.47.0)
	/System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 600.0.0)
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 728.13.0)
	/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1259.0.0)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

[michaelld (Michael Dickens)]

Thanks. That info confirmed my suspicion of where the issue was.

I just pushed a rev-bump that should fix this issue, in r150789 and r150790. I'm going to close this ticket as 'fixed'. You'll want to do:

sudo port selfupdate
sudo port upgrade glfw gr-fosphor

to get the changes.

[michael.kirkhart@…]

Yep, that took care of the problem. Thank you so much for fixing this.