gr-limesdr 3.0.1 Failed to build gr-limesdr on MacOS 10.15.6

[melfvelin (Martin Elfvelin)]

When trying to install gr-limesdr I get the following:

Error: Failed to build gr-limesdr: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_gr-limesdr/gr-limesdr/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gr-limesdr failed

I've installed Xcode, command line tools, MacPorts, gnuradio with all dependencies as well as limesuite through macports. Everyting installed from scratch within the last couple of days. After failing to build gr-limesdr I've run the following:

sudo port selfupdate
sudo port upgrade outdated
sudo port clean gr-limesdr
sudo port -t install gr-limesdr (also fails)

Still produces the same error. Next I realized that gr-limesdr is only compatible with gnuradio 3.7 so I cleaned gnuradio through macports and installed gnuradio 3.7 via ​https://github.com/ktemkin/gnuradio-for-mac-without-macports but still get the same error when trying to install gr-limesdr through macports so perhaps this ticket will still be useful.

[chrstphrchvz (Christopher Chavez)]

:info:build ModuleNotFoundError: No module named 'six'

Looks like a missing build dependency on port:py{active_python_version_no_dot}-six.

[chrstphrchvz (Christopher Chavez)]

Next I realized that gr-limesdr is only compatible with gnuradio 3.7…

If that is the case, then shouldn't the port specify a dependency on the gnuradio37 port rather than gnuradio?

[chrstphrchvz (Christopher Chavez)]

Replying to chrstphrchvz:

Next I realized that gr-limesdr is only compatible with gnuradio 3.7…

If that is the case, then shouldn't the port specify a dependency on the gnuradio37 port rather than gnuradio?

See [167079b0ca/macports-ports]: using gnuradio 3.8 was intentionally allowed.

[chrstphrchvz (Christopher Chavez)]

Replying to chrstphrchvz:

:info:build ModuleNotFoundError: No module named 'six'

Looks like a missing build dependency on port:py{active_python_version_no_dot}-six.

Never mind; pyXX-six is already considered a dependency for building gr-limesdr. I am unable to reproduce or explain the reporter's error.

[melfvelin (Martin Elfvelin)]

Shooting from the hip here but I tried to install py-six and try again:

sudo port install py-six
--->  Computing dependencies for py-six
--->  Fetching archive for py-six
--->  Attempting to fetch py-six-1.15.0_0.darwin_19.noarch.tbz2 from https://packages.macports.org/py-six
--->  Attempting to fetch py-six-1.15.0_0.darwin_19.noarch.tbz2.rmd160 from https://packages.macports.org/py-six
--->  Installing py-six @1.15.0_0
--->  Activating py-six @1.15.0_0
--->  Cleaning py-six
--->  Scanning binaries for linking errors
--->  No broken files found.                             
--->  No broken ports found.
martinelfvelin@MacBook-Air-som-tillhor-Martin Desktop % sudo port install gr-limesdr
--->  Computing dependencies for gr-limesdr
--->  Fetching archive for gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python37.darwin_19.x86_64.tbz2 from https://packages.macports.org/gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python37.darwin_19.x86_64.tbz2 from https://cph.dk.packages.macports.org/gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python37.darwin_19.x86_64.tbz2 from https://lil.fr.packages.macports.org/gr-limesdr
--->  Building gr-limesdr
Error: Failed to build gr-limesdr: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_gr-limesdr/gr-limesdr/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gr-limesdr failed

[ra1nb0w]

Use sudo port install gr-limesdr +python38 I am waiting michaelld's answer about the move of gnuradio to python 3.8

[melfvelin (Martin Elfvelin)]

sudo port install gr-limesdr +python38 
--->  Computing dependencies for gr-limesdr
--->  Fetching archive for gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python38.darwin_19.x86_64.tbz2 from https://packages.macports.org/gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python38.darwin_19.x86_64.tbz2 from https://cph.dk.packages.macports.org/gr-limesdr
--->  Attempting to fetch gr-limesdr-3.0.1_1+docs+python38.darwin_19.x86_64.tbz2 from https://lil.fr.packages.macports.org/gr-limesdr
--->  Fetching distfiles for gr-limesdr
--->  Verifying checksums for gr-limesdr
--->  Extracting gr-limesdr
--->  Configuring gr-limesdr
--->  Building gr-limesdr
--->  Staging gr-limesdr into destroot
--->  Installing gr-limesdr @3.0.1_1+docs+python38
--->  Activating gr-limesdr @3.0.1_1+docs+python38
--->  Cleaning gr-limesdr
--->  Scanning binaries for linking errors
--->  No broken files found.                             
--->  No broken ports found.

Cheers guys, thanks for the quick responses.

[michaelld (Michael Dickens)]

Sorry about that mess-up on my end folks! I didn't move the GR-OOTs to +python38, because I was still testing GR +python38 and hoping that we can fix the process spawning issue from a Python38 change ... but my "real job" takes priority and I just never got back to this, at least not in a timely manner.

I'm reverting the GR default variants back to +python37 and leaving the GR-OOTs as-is. That will resolve this issue in a specific sense, and I'm glad @rainb0w jumped in to help out here & that there is a solution for folks who need it: just select the same +pythonXY variant as GR!

[michaelld (Michael Dickens)]

In c7fc6dd778fa4976fa6d1de623e988118e461c44/macports-ports (master):

gnuradio: revert back to +python37 as the default variant; rev-bump

Closes: #61173

1) GR-OOTs require the same variant, so they need to be switched that the same time as GR proper's variant is switched. My bad there!

2) Py38 has some changes to how processes are spawned that causes issues with some GR functionality. Leave Py38 as an option for users who need it and are not impacted by the issue, but keep the default at Py37 since it does not have this specific process spawning issue. Hope for a fix ...