Changes between Version 9 and Version 10 of Documentation/dSDR/GNURadio/Installation31Debian


Ignore:
Timestamp:
Oct 18, 2013, 10:41:14 PM (11 years ago)
Author:
ssugrim
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/dSDR/GNURadio/Installation31Debian

    v9 v10  
    1 = Installation of GNU radio software on a orbit node with the baseline.ndz image =
    2 
    3 == Binary Packages ==
     1== Installation of GNU radio software on a orbit node with the baseline.ndz image ==
     2
     3=== Binary Packages ===
    44
    55Baseline.ndz installs a slimed version of Debian, for image speed. There is a binary package of GNU radio in the Debian repository, but it
    … …  
    1818these packages is http://gnuradio.org/redmine/wiki/1/DebianPackages
    1919
    20 == Building  from sources ==
     20=== Building  from sources ===
    2121
    2222This section explains how to build the GNU Radio software from sources. It is loosely modeled after the instructions from http://gnuradio.org/redmine/wiki/gnuradio/UbuntuInstall . As noted before, however, we're installing on a Debian system, so the process is a little different. 
    2323
    24 === Prerequisites ===
     24==== Prerequisites ====
    2525Before we build the actual Gnu radio we must satisfy this list of  prerequisites:
    2626 * sdcc-libraries_2.6.0-5
    … …  
    6363'''Note:''' Our architecture is i686, but the only debs for i386. We have used the i386 ones sucessfully. The install process was the same as for the libraries.
    6464
    65 === Sources ===
     65==== Sources ====
    6666
    6767Once we have all the dependencies in place, we can begin building the actual GNU Radio software. There are many ways to get the sources. The most straight forward
    6868is to download the file from http://gnuradio.org/redmine/wiki/gnuradio/Download. If you are using the node's console you can use [http://en.wikipedia.org/wiki/Wget wget]. As an alternative you can download the file to some other machine, and them copy file to the node with [http://help.ischool.washington.edu/faqs/30_32_en.html scp].   Once you have the source on your node you'll need to extract it ([http://www.tech-recipes.com/rx/65/decompress-and-extract-a-tgz-or-targz-archive-in-a-single-step/ refrence]).
    6969
    70 === Building ===
     70==== Building ====
    7171
    7272If you copied from the development repositories (svn or git) you man need to run '''./bootstrap'''. Once bootstrap completes you will need to run '''./configure'''. Once completed a list of components being built will be displayed:
    … …  
    121121}}}
    122122
    123 === Post Build setup ===
     123==== Post Build setup ====
    124124
    125125Once you have correctly built executables, there are a few modification to be made before you can run the examples. These may all be optional, if you encounter errors when you try to use the executables one of these changes may fix it.
    126126
    127 ==== Create USRP Group ====
     127===== Create USRP Group =====
    128128Follow these steps to create a usrp group. This is need to have udev ([http://en.wikipedia.org/wiki/Udev reference]) enumerate the USRP properly.
    129129{{{
    … …  
    141141}}}
    142142
    143 ==== Adding  PYTHONPATH ====
     143===== Adding  PYTHONPATH =====
    144144This path is needed for some of the examples. (and perhaps your own blocks)
    145145
    … …  
    148148}}}
    149149
    150 ==== libtool modification ====
     150===== libtool modification =====
    151151There was a problem with earlier versions of Debian/Ubuntu's linker ([http://en.wikipedia.org/wiki/GNU_linker refrence]). It was resolved with this fix:
    152152{{{
    … …  
    167167
    168168
    169 === Running Examples ===
     169==== Running Examples ====
    170170
    171171Assuming you have x11 exports correctly configured ([http://solaris.reys.net/how-to-x11-forwarding-using-ssh-putty-and-xming/ reference]) you can use the live FFT to see some