Has anyone experienced any build failures in UHD on Ubuntu 13.04 using
build-gnuradio?
I haven’t upgraded my Ubuntu system yet, and I have had one report of a
UHD build failure on Ubuntu 13.04
due to libboost1.49, but a manual upgrade to libboost1.53 cured it.
–
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
On Fri, May 3, 2013 at 4:37 AM, Marcus D. Leech [email protected]
wrote:
Has anyone experienced any build failures in UHD on Ubuntu 13.04 using
build-gnuradio?
I haven’t upgraded my Ubuntu system yet, and I have had one report of a
UHD build failure on Ubuntu 13.04
due to libboost1.49, but a manual upgrade to libboost1.53 cured it.
Hi Marcus,
I have installed both UHD and gnuradio on several xubuntu 13.04
computers having the default boost 1.49. No build issues and no
runtime issues, though haven’t done much testing so far.
Alex
On 05/03/2013 08:59 AM, Sean Nowlan wrote:
and haven’t had any issues yet (knock on wood!).
(Sorry - forgot to copy to list)
On 03 May 2013 09:00, Sean Nowlan wrote:
On 05/03/2013 08:59 AM,
Sean Nowlan wrote:
On 05/02/2013 10:37 PM, Marcus D. Leech wrote:
Has anyone experienced any build failures in UHD on Ubuntu
13.04 using
build-gnuradio?
I haven’t upgraded my Ubuntu
system yet, and I have had one report of a
UHD build failure on
Ubuntu 13.04
due to libboost1.49, but a manual upgrade to
libboost1.53 cured it.
I didn’t try to build with Boost 1.49. I went
straight to Boost 1.53 and haven’t had any issues yet (knock on
wood!).
(Sorry - forgot to copy to list)
OK, so the question I have
lingering in my head is whether I should special-case Ubuntu 13.04, and
have it explicitly install Boost1.53. I have one report of grief with
UHD+Ubuntu-13.04+boost-1.49, and reports of it having gone just fine
with boost-1.49 on Ubuntu 13.04.
I updated the GNURadio Ubuntu install instructions for the 1.53 special
case. It’s a known safe option, so it should generate less issues.
I’ll update the wiki once Ubuntu updates the libboost-all-dev
meta-package
to the newer version.
Cheers,
Ben
I found a different issue with Ubuntu 13.04 - if both qt 4.8 and 5.0
are installed, cmake will disable the qtgui component because it will
only find Qt 5. There is probably a simple solution but i haven’t had
the time to look at it.
Alex
On Mon, May 6, 2013 at 12:38 PM, Alexandru C. [email protected]
wrote:
I found a different issue with Ubuntu 13.04 - if both qt 4.8 and 5.0
are installed, cmake will disable the qtgui component because it will
only find Qt 5. There is probably a simple solution but i haven’t had
the time to look at it.
It looks like this problem can be solved by installing the qt4-default
package.
Alex