Opened 11 years ago

Closed 11 years ago

#38274 closed defect (worksforme)

gnuradio +full installs without gnuradio-companion

Reported by: vladshikhov@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc:
Port: gnuradio

Description (last modified by ryandesign (Ryan Carsten Schmidt))

When I install gnuradio +full variant it lacks gnuradio-companion.

According http://lists.gnu.org/archive/html/discuss-gnuradio/2013-01/msg00079.html I installed boost 1.51

So I have:

>port installed boost
The following ports are currently installed:
  boost @1.51.0_1+no_single+no_static+python27 (active)

and after I install gnuradio (+full variant) it lack the gnuradio-companion (and also, during install process it installs boost-1.52.0_1+no_single+no_static+python27 ignoring my active boost version 1.51)

Change History (7)

comment:1 Changed 11 years ago by vladshikhov@…

Cc: vladshikhov@… added

Cc Me!

comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: vladshikhov@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to michaelld@…

If you want MacPorts not to upgrade dependencies, you need to use the -n flag (sudo port -n install gnuradio). Use this option extremely carefully, i.e. only when you know exactly what dependencies would be upgraded and that you don't want them to be upgraded. Defeating MacPorts' dependency upgrade feature can cause problems. You can use the dry-run option -y to see what would happen (sudo port -y install gnuradio).

comment:3 in reply to:  2 Changed 11 years ago by vladshikhov@…

It seems not works for me.

sudo port -n install gnuradio +full

---> Computing dependencies for gnuradio ---> Dependencies to be installed: boost uhd ---> Fetching archive for boost ---> Attempting to fetch boost-1.52.0_1+no_single+no_static+python27.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/boost

Replying to ryandesign@…:

If you want MacPorts not to upgrade dependencies, you need to use the -n flag (sudo port -n install gnuradio). Use this option extremely carefully, i.e. only when you know exactly what dependencies would be upgraded and that you don't want them to be upgraded. Defeating MacPorts' dependency upgrade feature can cause problems. You can use the dry-run option -y to see what would happen (sudo port -y install gnuradio).

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

Strange. Then "port -n install" works for me quite well. Maybe:

sudo port selfupdate
sudo port clean gnuradio
sudo port -n install gnuradio +full

The basic issue is that Boost 1.52 is banned by GNU Radio's CMake build script because its threading is messed up; it worked in 1.51, and will again in 1.53 once MacPorts' boost is updated to that version. Given that boost 1.53 has been out for quite a while now, I'm wondering what the status of that upgrade is ...

comment:5 in reply to:  4 Changed 11 years ago by vladshikhov@…

I've tried once again as you wrote step by step, but got the same result.

Replying to michaelld@…:

Strange. Then "port -n install" works for me quite well. Maybe:

sudo port selfupdate
sudo port clean gnuradio
sudo port -n install gnuradio +full

The basic issue is that Boost 1.52 is banned by GNU Radio's CMake build script because its threading is messed up; it worked in 1.51, and will again in 1.53 once MacPorts' boost is updated to that version. Given that boost 1.53 has been out for quite a while now, I'm wondering what the status of that upgrade is ...

comment:6 in reply to:  4 Changed 11 years ago by vladshikhov@…

Complete deleting /opt and reinstalling everything did the job.

Replying to michaelld@…:

Strange. Then "port -n install" works for me quite well. Maybe:

sudo port selfupdate
sudo port clean gnuradio
sudo port -n install gnuradio +full

The basic issue is that Boost 1.52 is banned by GNU Radio's CMake build script because its threading is messed up; it worked in 1.51, and will again in 1.53 once MacPorts' boost is updated to that version. Given that boost 1.53 has been out for quite a while now, I'm wondering what the status of that upgrade is ...

comment:7 Changed 11 years ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: newclosed

Fascinating. I've no idea why deleting /opt might have worked, but I'm glad it did.

Note: See TracTickets for help on using tickets.