OpenBTS: Ubuntu Install
* Sign in * Register
* Home * Projects * Help
Search: GNU Radio
* Overview * Activity * Roadmap * Issues * News * Documents * Wiki * Files * Repository
Wiki Start page Index by title Index by date History GNU Radio Release 3.2¶
With the latest GNU Radio release 3.2, binary package installation is available for Ubuntu 9.04 (Jaunty), bypassing the need for manually installing build tool prerequisites and performing a source code installation. In addition, installation and configuration of the USRP and USRP2 is automated. This is fastest and easiest way to get a working GNU Radio platform.
The rest of this page is now somewhat outdated and needs some reorganization. Installation Options¶
This page provides information and scripts to compile and install GNU Radio and its required background applications, libraries, and includes on Ubuntu Linux 6.10 ("Edgy") or newer; they can probably be applied to some previous versions, though that hasn't been tested.
Installation on Ubuntu 6.10 ("Edgy") can be completed for the most part using binary packages and a package manager, but some packages must be downloaded and compiled from source.
Installation on Ubuntu 7.04 ("Feisty") or newer systems can be completed entirely using binary packages and a package manager, or may be done by download and source compile.
NOTE: The official releases of GNU Radio, version 3.0.3 or earlier, will *NOT* reliably function on Feisty when using a USRP; the USRP will work once, then fail and require the USRP to be power cycled or Ubuntu to be rebooted. Fixes for correct functionality are available in the SVN trunk. Pre-Requisites for Source Build¶
The following packages are required for compiling various parts of GNU Radio on Ubuntu. These packages can be installed via "synaptic", "dselect", or "apt-get". Use the latest versions of all packages unless otherwise noted.
* Development Tools (need for compilation)
o g++
o subversion
o make
o autoconf, automake, libtool
o sdcc (from "universe"; 2.4 or newer)
o guile (1.6 or newer)
o ccache (not required, but recommended if you compile frequently)
* Libraries (need for runtime and for compilation)
o python-dev
o FFTW 3.X (fftw3, fftw3-dev)
o cppunit (libcppunit and libcppunit-dev)
o Boost 1.35 (or later)
o libusb and libusb-dev
o wxWidgets (wx-common) and wxPython (python-wxgtk2.8)
o python-numpy (via python-numpy-ext) (for SVN on or after 2007-May-28)
o ALSA (alsa-base, libasound2 and libasound2-dev)
o Qt (libqt3-mt-dev for versions earlier than 8.04; version 4 works for 8.04 and later)
o SDL (libsdl-dev)
o GSL GNU Scientific Library (libgsl0-dev >= 1.10 required for SVN trunk, not in binary repositories for 7.10 and earlier)
* SWIG (1.3.31 or newer required)
o Edgy or previous: requires installation from source
o Feisty or newer: use the standard package install (swig)
* QWT (optional) (5.0.0 or newer required)
o Must be installed from source (as of 2008-01-15).
o qt4 versions should be used for 8.04 and 8.10. DO! : sudo apt-get update and then upgrade for a proper qt4.
* QWT Plot3d Lib
o Must be installed for gr-qtgui to work. qt4 version preferred for Ubuntu 8.04 and 8.10
* Polyphase Filter Bank examples
o for the examples in gnuradio-examples/python/pfb to work you need to install python-scipy, python-matplotlib, and python-tk
* Other useful packages
o doxygen (for creating documentation from source code)
o octave (from "universe")
Install Scripts¶
The following are scripts to take most users through a GNU Radio install on a typical Ubuntu install, with the hope that it provides enough guidance such that you can get GNU Radio up and running on your Ubuntu box.
- This section is for Edgy or previous only (no changes are needed on Feisty or newer, except possibly to disable the CDROM entry):
Manually uncomment all repositories to include "universe" and "multiverse" either via direct editing
sudo <EDITOR> /etc/apt/sources.list
or via the provided GUI: System -> Administration -> Software Sources. Then enter the admin password for access. On the "Ubuntu" tab, make sure all of "main restricted universe multiverse" are checked and the rest unchecked (or deal with those are you deem correct for your setup). Click "Close", then "Reload" to update the package list. The uncommented lines of the file "/etc/apt/sources.list" should read something like (DIST is a string with your particular distribution: edgy, feisty, gusty, etc):
deb http://us.archive.ubuntu.com/ubuntu/ DIST main restricted universe multiverse deb http://us.archive.ubuntu.com/ubuntu/ DIST-updates main restricted universe multiverse deb http://security.ubuntu.com/ubuntu/ DIST-security main restricted universe multiverse
Update the local dpkg cache:
sudo apt-get update
Install required packages (some are likely already installed by Ubuntu by default; some are likely redundant with others; but these groups cover all of the required packages, except for in Edgy)
- Lucid (10.04):
sudo apt-get -y install libfontconfig1-dev libxrender-dev libpulse-dev swig g++ automake libtool python-dev libfftw3-dev \ libcppunit-dev libboost-all-dev libusb-dev fort77 sdcc sdcc-libraries \ libsdl1.2-dev python-wxgtk2.8 subversion git-core guile-1.8-dev \ libqt4-dev python-numpy ccache python-opengl libgsl0-dev \ python-cheetah python-lxml doxygen qt4-dev-tools \ libqwt5-qt4-dev libqwtplot3d-qt4-dev pyqt4-dev-tools
- Karmic (9.10):
sudo apt-get -y install swig g++ automake libtool python-dev libfftw3-dev \ libcppunit-dev libboost1.38-dev libusb-dev fort77 sdcc sdcc-libraries \ libsdl1.2-dev python-wxgtk2.8 subversion git-core guile-1.8-dev \ libqt4-dev python-numpy ccache python-opengl libgsl0-dev \ python-cheetah python-lxml doxygen qt4-dev-tools \ libqwt5-qt4-dev libqwtplot3d-qt4-dev pyqt4-dev-tools
- Jaunty (9.04): **Package sdcc-nf needs to be installed (instead of sdcc)**
sudo apt-get -y install swig g++ automake1.9 libtool python-dev fftw3-dev \ libcppunit-dev libboost1.35-dev sdcc-nf libusb-dev \ libsdl1.2-dev python-wxgtk2.8 subversion git guile-1.8-dev \ libqt4-dev python-numpy ccache python-opengl libgsl0-dev \ python-cheetah python-lxml doxygen qt4-dev-tools \ libqwt5-qt4-dev libqwtplot3d-qt4-dev pyqt4-dev-tools
If you are upgrading from an older install, you may have python-wxgtk2.6 installed.
Because python-wxgtk2.6 takes precedence over python-wxgtk2.8, it must be removed: sudo apt-get remove python-wxgtk2.6 * Intrepid (8.10): **Package sdcc-nf needs to be installed (instead of sdcc)**
sudo apt-get -y install swig g++ automake1.9 libtool python-dev fftw3-dev \ libcppunit-dev libboost1.35-dev sdcc-nf libusb-dev \ libsdl1.2-dev python-wxgtk2.8 subversion git guile-1.8-dev \ libqt4-dev python-numpy ccache python-opengl libgsl0-dev \ python-cheetah python-lxml doxygen qt4-dev-tools \ libqwt5-qt4-dev libqwtplot3d-qt4-dev pyqt4-dev-tools
- Hardy (8.04): **Boost should be installed as explained in README.building-boost file **
sudo apt-get -y install swig g++ automake1.9 libtool python-dev fftw3-dev \ libcppunit-dev sdcc libusb-dev libasound2-dev libsdl1.2-dev \ python-wxgtk2.8 subversion guile-1.8-dev libqt4-dev python-numpy-ext \ ccache python-opengl libgsl0-dev python-cheetah python-lxml doxygen \ libqwt5-qt4-dev libqwtplot3d-qt4-dev qt4-dev-tools pyqt4-dev-tools
- Gutsy (7.10): **Boost should be installed as explained in README.building-boost file. GSL is required Also **
sudo apt-get -y install g++ automake libtool python-dev fftw3-dev \ libcppunit-dev sdcc libusb-dev libasound2-dev \ libsdl1.2-dev python-wxgtk2.8 subversion guile-1.8-dev libgsl0-dev \ libqt3-mt-dev python-numpy-ext swig ccache
- Feisty (7.04): **Boost should be installed as explained in README.building-boost file. GSL is required Also **
sudo apt-get -y install g++ automake1.9 libtool python-dev fftw3-dev \ libcppunit-dev sdcc libusb-dev libasound2-dev \ libsdl1.2-dev python-wxgtk2.8 subversion guile-1.6-dev\ libqt3-mt-dev python-numpy-ext swig ccache
- Edgy (6.10): **It is strongly recommended that you use one of the newer releases above**
sudo apt-get -y install g++ automake1.9 libtool python-dev fftw3-dev \ libcppunit-dev libboost-dev sdcc libusb-dev libasound2-dev \ libsdl1.2-dev python-wxgtk2.6 subversion guile-1.6-dev \ libqt3-mt-dev python-numpy-ext ccache
Note that above line for Edgy installs python-wxgtk-2.6. While this is good enough for older gnuradio releases, it is too old for recent gnuradio svn snapshots. If you want to build a recent svn snapshot of gnuradio you need wxgtk version 2.8 or later.
You can install more recent wxgtk versions from the wxwidgets debian and ubuntu repository.
See Installing latest wxgtk-2.8 packages on debian or Ubuntu Install optional packages, if desired; some might already be installed from the previous command:
sudo apt-get -y install gkrellm wx-common libwxgtk2.8-dev alsa-base autoconf xorg-dev g77 gawk bison openssh-server emacs cvs usbview octave
For Edgy only: Get, Compile, and Install SWIG
wget http://prdownloads.sourceforge.net/swig/swig-1.3.33.tar.gz tar zxf swig-1.3.33.tar.gz cd swig-1.3.33 ./configure make sudo make install cd ..
Optional: Get, Compile, Install QWT 5.0.0 (or newer): * NOTE: You should not need to set the environment variables "QTDIR" or "QWT_CFLAGS", so leave them be (for now).
wget http://superb-east.dl.sourceforge.net/sourceforge/qwt/qwt-5.0.2.tar.bz2 tar jxf qwt-5.0.2.tar.bz2 cd qwt-5.0.2
- Now edit qwtconfig.pri: ** Change the unix version of "INSTALLBASE" to "/usr/local" (was "/usr/local/qwt-5.0.2"); ** Change "doc.path" to "$$INSTALLBASE/doc/qwt" (was "$$INSTALLBASE/doc"); ** Save, exit.
The "doc" portion is in both HTML and man-style, but is all in /usr/local/doc/{html,man}. While this isn't the standard path, there doesn't seem to be an easy way to separate them and thus this is left as is. Then:
qmake make sudo make install cd ..
Install Boost¶
For Ubuntu 8.04 and older, download and install Boost 1.35 or later as follows (see README.building-boost file):
1) Download the latest version of boost from boost.sourceforge.net (boost_1_37_0.tar.bz2 was the latest when this was written). 2) unpack it somewhere and cd into the resulting directory
$ cd boost_1_37_0
3) Pick a prefix to install it into. For example use /opt/boost_1_37_0
$ BOOST_PREFIX=/opt/boost_1_37_0
4) Configure
$ ./configure --prefix=$BOOST_PREFIX --with-libraries=thread,date_time,program_options
5) Compile the package
$ make
6) Install the package
$ sudo make install
$ cd ..
Installing GNU Radio¶ Download, bootstrap, configure, and compile GNU Radio package:
- Install GNU Radio from git
git clone http://gnuradio.org/git/gnuradio.git
cd gnuradio export LD_LIBRARY_PATH=$BOOST_PREFIX/lib # As per the instructions for installing Boost
./bootstrap ./configure --with-boost=$BOOST_PREFIX # As per the instructions for installing Boost make
Optionally: Run the GNU Radio software self-check; does not require a USRP.
make check
If any test or tests do not work, GNU Radio might still function properly, but it might be wise to look in the email archives for a fix or to write the email list. If writing to the email list, please include the OS type, OS version, and CPU type (e.g. via "uname -a"), anything special about the computer hardware, software versions (gcc, g++, swig, sdcc, etc) and how installed (standard or non-standard package, source). Now install GNU Radio for general use (default is in to /usr/local ):
sudo make install
Ubuntu uses udev for handling hotplug devices, and does not by default provide non-root access to the USRP. The following script is taken from directions, and sets up groups to handle USRP via USB, either live or hot-plug
sudo addgroup usrp sudo usermod -G usrp -a <YOUR_USERNAME> echo 'ACTION=="add", BUS=="usb", SYSFS{idVendor}=="fffe", SYSFS{idProduct}=="0002", GROUP:="usrp", MODE:="0660"' > tmpfile sudo chown root.root tmpfile sudo mv tmpfile /etc/udev/rules.d/10-usrp.rules
- At this point, Ubuntu is configured to know what to do if/when it detects the USRP on the USB, except that "udev" needs to reload the rules to include the newly created one. The following might work, but if it doesn't then rebooting the computer will.
sudo udevadm control --reload-rules
or
sudo /etc/init.d/udev stop sudo /etc/init.d/udev start
or
sudo killall -HUP udevd
You can check if the USRP is being recognized, by examining /dev/bus/usb after plugging in a USRP. Using the command:
ls -lR /dev/bus/usb | grep usrp
should result in one or more lines (one for each USRP) reading something like:
crw-rw---- 1 root usrp 189, 514 Mar 24 09:46 003
Each device file will be listed with group 'usrp' and mode 'crw-rw----'.
* NOTE: If installing on Feisty or newer, the computer probably needs to be rebooted in order for the GNU Radio software to interface correctly with the USRP hardware. This does not seem to be necessary on Edgy.
Once you've verified that the USRP is available to Ubuntu, now it is time to verify that GNU Radio works with the USRP (if installed; if not, skip this). While "usrp_benchmark_usb" might not return a full 32 MB/s of throughput, the script should at least run properly; if not, either GNU Radio didn't make correctly or the USRP isn't accessible. From the "gnuradio" directory, verify that all of the following work:
- Python interface to the USRP; provides a rough estimate of the maximum throughput (quantized to a power of 2) between the host computer and the USRP.
cd gnuradio-examples/python/usrp ./usrp_benchmark_usb.py
- C++ interface to the USRP; provides a good estimate of the maximum throughput (non-quantized) between the host computer and the USRP.
cd usrp/host/apps ./test_usrp_standard_tx ./test_usrp_standard_rx
Update the rest of the system, after which you might need or want to reboot:
sudo apt-get -y upgrade
Update the Linux distro, after which a reboot is required:
sudo apt-get -y dist-upgrade
Broken libtool on Debian and Ubuntu¶
Because Debian and Ubuntu apply a poorly implemented "enhancement" to the upstream version of libtool, they break the ability to test code and libraries prior to installing them. We think that testing before installation is a good idea. To work around their damage, be sure to include $PREFIX/lib (and $PREFIX/lib64 on 64-bit machines) in /etc/ld.so.conf.
If you don't include $PREFIX/lib in /etc/ld.so.conf, you will see errors during the linking phase of the build. There are several places it shows up. The first one is often during the build of mblocks. It's not an mblock problem. It's a Debian/Ubuntu problem.
Do this to work around this "feature": 1) Make a copy from the current ld.so.conf file and save it in a temp folder:
cp /etc/ld.so.conf /tmp/ld.so.conf
2) Add /usr/local/lib path to it :
echo /usr/local/lib >> /tmp/ld.so.conf
3) If you installed Boost (version 1_37_0 for example) manually, then add its library path to the file:
echo /opt/boost_1_37_0/lib >> /tmp/ld.so.conf
4) Delete the original ld.so.conf file and put the modified file instead:
sudo mv /tmp/ld.so.conf /etc/ld.so.conf
5) Do ldconfig:
sudo ldconfig