[MacPorts] #49919: gr-osmosdr is still broken after rebuilding it more than 3 times.

[MacPorts]

#49919: gr-osmosdr is still broken after rebuilding it more than 3 times.
-------------------------+-------------------------
  Reporter:  ton@…       |      Owner:  michaelld@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.4
Resolution:              |   Keywords:
      Port:  gr-osmosdr  |
-------------------------+-------------------------

Comment (by njm7176@…):

 Replying to [comment:9 ton@…]:
 > gr-osmosdr builds fine now, however when launching anything that uses
 osmosdr i still get the same message as above.
 >
 You may also have a python issue, not one with with osmocom or gnuradio.

 In the above error, osmocom_fft (macports) is trying to use osmosdr
 modules in '''/usr/local''' (system/homebrew) directory.  All the stuff
 macports just built for you reside somewhere in '''/opt/local'''

 Check:
 {{{
 echo $PYTHONPATH
 }}}
 You should see the following macports python directories:
 {{{
 /opt/local/lib/python2.7/site-packages
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/
 }}}
 If not, try the following, and add it to your .profile if it seems to do
 the trick:
 {{{
 export PYTHONPATH=/opt/local/lib/python2.7/site-
 packages:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/:$PYTHONPATH
 }}}
 Results may vary, but apart from issues with gr-osmosdr and doxygen
 ([https://trac.macports.org/ticket/49881 49881]), I did a full reinstall
 of gnuradio via macports this weekend and everything appears behaving
 normally so far...

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