Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#51803 closed defect (fixed)

gr-fosphor @20160522_0: rev-upgrade considers it broken

Reported by: particlephysics08@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: gr-fosphor

Description

Output of sudo port install gr-fosphor requested I send this in as a bug.

Attachments (2)

fosphorbug (282.9 KB) - added by particlephysics08@… 8 years ago.
text file with stderr output of "port -d -y rev-upgrade"
port-output.txt (516 bytes) - added by camusny@… 8 years ago.
gr-fosphor and port rev-upgrade output

Download all attachments as: .zip

Change History (17)

Changed 8 years ago by particlephysics08@…

Attachment: fosphorbug added

text file with stderr output of "port -d -y rev-upgrade"

comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to michaelld@…
Summary: Cannot install on OSXgr-fosphor @20160522_0: rev-upgrade considers it broken

The first page of the log says:

DEBUG: Marking /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gnuradio/fosphor/_fosphor_swig.so as broken
DEBUG: Marking /opt/local/lib/libgnuradio-fosphor.3.7.0git.dylib as broken
DEBUG: Broken: gr-fosphor

So this looks like output from rev-upgrade, the process that MacPorts runs after every installation to see if anything is broken. On your system, it detected the gr-fosphor port was broken for some reason. Normally MacPorts would then rebuild that port. But your log ends with:

Warning: If this was no dry run, rev-upgrade would now run the checks again to find unresolved and newly created problems

This suggests you ran port using the -y flag, which tells MacPorts to not actually make any changes.

comment:2 Changed 8 years ago by michaelld (Michael Dickens)

What do the following return:

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

comment:3 Changed 8 years ago by michaelld (Michael Dickens)

The OP replied off-ticket with the otool info. According to it, the actual issue is linkage with GLFW:

lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0)

Thus, what do the following return:

port installed "glfw*"
otool -L /opt/local/lib/libglfw.dylib

comment:4 Changed 8 years ago by michaelld (Michael Dickens)

And, would you mind replying on-ticket next time? It's easier to track all of the various info here. Thx!

comment:5 Changed 8 years ago by michaelld (Michael Dickens)

At least for me (10.11 latest), glfw and glfw-devel both install with the correct library info. Hence, maybe your glfw install needs to be updated & then gr-fosphor reinstalled.

comment:6 Changed 8 years ago by particlephysics08@…

vorlok$ port installed "glfw*" The following ports are currently installed:

glfw @3.2_0+docs (active)

vorlok$ 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 21.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 1153.18.0) /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.8.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1348.17.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 62.0.0) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1154.0.0) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

Apologies for replying in the mailing list.

comment:7 Changed 8 years ago by particlephysics08@…

Is this what you meant?

vorlok$ sudo port upgrade glfw Password: ---> Scanning binaries for linking errors ---> Found 2 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order

gr-fosphor @20160522

---> Computing dependencies for gr-fosphor ---> Cleaning gr-fosphor ---> Scanning binaries for linking errors ---> Found 2 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order

gr-fosphor @20160522

---> Computing dependencies for gr-fosphor ---> Fetching distfiles for gr-fosphor ---> Verifying checksums for gr-fosphor ---> Extracting gr-fosphor ---> Applying patches to gr-fosphor ---> Configuring gr-fosphor ---> Building gr-fosphor ---> Staging gr-fosphor into destroot ---> Deactivating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Uninstalling gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Computing dependencies for gr-fosphor ---> Installing gr-fosphor @20160522_0 ---> Activating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 2 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order

gr-fosphor @20160522

---> Computing dependencies for gr-fosphor ---> Fetching distfiles for gr-fosphor ---> Verifying checksums for gr-fosphor ---> Extracting gr-fosphor ---> Applying patches to gr-fosphor ---> Configuring gr-fosphor ---> Building gr-fosphor ---> Staging gr-fosphor into destroot ---> Deactivating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Uninstalling gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Computing dependencies for gr-fosphor ---> Installing gr-fosphor @20160522_0 ---> Activating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 2 broken file(s), matching files to ports Error: Port gr-fosphor is still broken after rebuilding it more than 3 times. Error: Please run port -d -y rev-upgrade and use the output to report a bug. Port gr-fosphor still broken after rebuilding 3 time(s)

while executing

"error "Port $portname still broken after rebuilding [expr {$broken_port_counts($portname) - 1}] time(s)""

(procedure "revupgrade_scanandrebuild" line 280) invoked from within

"revupgrade_scanandrebuild broken_port_counts $opts"

(procedure "macports::revupgrade" line 5) invoked from within

"macports::revupgrade $opts"

(procedure "action_revupgrade" line 2) invoked from within

"action_revupgrade $action $portlist $opts"

(procedure "action_upgrade" line 25) invoked from within

"$action_proc $action $portlist [array get global_options]"

(procedure "process_cmd" line 103) invoked from within

"process_cmd $remaining_args"

invoked from within

"if { [llength $remaining_args] > 0 } {

# If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5268)

Changed 8 years ago by camusny@…

Attachment: port-output.txt added

gr-fosphor and port rev-upgrade output

comment:8 in reply to:  description ; Changed 8 years ago by camusny@…

Replying to particlephysics08@…:

Output of sudo port install gr-fosphor requested I send this in as a bug.

Same situation. I wonder if it has to do with my brew and MacPorts coexistence on this Mac.

Let's move towards a solution on this.

comment:9 Changed 8 years ago by particlephysics08@…

I, too, have brew alongside port. Not enough overlap to go with just one.

comment:10 in reply to:  8 Changed 8 years ago by camusny@…

Replying to camusny@…:

Replying to particlephysics08@…:

Output of sudo port install gr-fosphor requested I send this in as a bug.

Same situation. I wonder if it has to do with my brew and MacPorts coexistence on this Mac.

Let's move towards a solution on this.

I ran 'port uninstall' and for gr-fosphor and glfw. Instead I installed 'glfw-devel' followed by gr-fosphor. I referenced this ​https://trac.macports.org/ticket/51618 - gr-fosphor installed successfully.

comment:11 Changed 8 years ago by particlephysics08@…

This gflw-devel workaround seems to have worked for me as well.

vorlok$ sudo port uninstall gr-fosphor Password: ---> Deactivating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Uninstalling gr-fosphor @20160522_0 ---> Cleaning gr-fosphor vorlok$ sudo port uninstall glfw ---> Deactivating glfw @3.2_0+docs ---> Cleaning glfw ---> Uninstalling glfw @3.2_0+docs ---> Cleaning glfw vorlok$ sudo port install "glfw-devel" ---> Fetching archive for glfw-devel ---> Attempting to fetch glfw-devel-20160701_0+docs.darwin_14.x86_64.tbz2 from https://packages.macports.org/glfw-devel ---> Attempting to fetch glfw-devel-20160701_0+docs.darwin_14.x86_64.tbz2.rmd160 from https://packages.macports.org/glfw-devel ---> Installing glfw-devel @20160701_0+docs ---> Activating glfw-devel @20160701_0+docs ---> Cleaning glfw-devel ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. vorlok$ sudo port install gr-fosphor Password: ---> Computing dependencies for gr-fosphor ---> Fetching archive for gr-fosphor ---> Attempting to fetch gr-fosphor-20160522_0.darwin_14.x86_64.tbz2 from https://packages.macports.org/gr-fosphor ---> Attempting to fetch gr-fosphor-20160522_0.darwin_14.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/gr-fosphor ---> Attempting to fetch gr-fosphor-20160522_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/gr-fosphor ---> Fetching distfiles for gr-fosphor ---> Verifying checksums for gr-fosphor ---> Extracting gr-fosphor ---> Applying patches to gr-fosphor ---> Configuring gr-fosphor ---> Building gr-fosphor ---> Staging gr-fosphor into destroot ---> Installing gr-fosphor @20160522_0 ---> Activating gr-fosphor @20160522_0 ---> Cleaning gr-fosphor ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. vorlok$

Well, closer anyway. dhcp-10-203-61-75:~ vorlok$ osmocom_fft Mac OS; Clang version 6.1.0 (clang-602.0.53); Boost_105900; UHD_003.009.004-MacPorts-Release

Error importing GNU Radio's wxgui. Please make sure gr-wxgui is installed.

comment:12 Changed 8 years ago by mf2k (Frank Schima)

@particlephysics08: Please use WikiFormatting and the Preview button so your Trac comments are readable.

comment:13 Changed 8 years ago by michaelld (Michael Dickens)

A few items:

(1) I'm glad using glfw-devel works for you. glfw should to, but whatever.

(2) we generally do not recommend using brew and MacPorts together, because brew installs by default into /usr/local, which is a standard search path for most build systems, while port installs into /opt/local, which is a nonstandard search path. Hence, by default the brew install will be found while the port one won't be. Thus, when building within port one has to be very careful & that's just not always easy or even doable. This combination may or not work; it's your risk much more than our obligation to make sure it does work, though we try our best.

(3) I'd guess that you have a brew-installed Python first in the search PATH. Hence, when you run anything requiring Python (e.g., osmocom_fft), it finds that version instead of the port Python. Unless you've set the PYTHONPATH to include the port Python stuff, none of it will be found. Best way to deal with this is to make sure that

port select python

is set to "python27" (active), and then that /opt/local/bin is at the head of the PATH variable.

Good luck!

comment:14 Changed 8 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

I just pushed a rev-bump that might fix this issue, in r150789. I'm going to close this ticket as 'fixed' since glfw-devel worked.

comment:15 Changed 8 years ago by michaelld (Michael Dickens)

and r150790 ... for gr-fosphor itself, to rebuild using the correct glfw ABI self-id. You'll want to do:

sudo port selfupdate
sudo port upgrade glfw gr-fosphor

to get the changes.

Note: See TracTickets for help on using tickets.