discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Gentoo build from CVS: success and notes


From: Mark S Petrovic
Subject: [Discuss-gnuradio] Gentoo build from CVS: success and notes
Date: Thu, 23 Jun 2005 10:02:09 -0700
User-agent: Mutt/1.5.6i

info/fyi

For the archives, some notes on building gnuradio from the current state
of CVS in a Gentoo 2005.0 environment.  I've now built gnuradio from CVS
and successfully run some OTA files referenced below.  Time to buy a USRP!

Below, "Gentoo emerge" is Gentoo parlance for "install" a particular software 
package.

- Gentoo 2005.0 stage2 build  
        - causes most of the system to be built from the ground up
        via source compilation, which took a couple (read a few) days.
        Some of this time was spent thrashing around and chin-scratching,
        wondering "what just happened?"

        - http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml   (terse, 
but good)

        - or 
http://www.gentoo.org/doc/en/handbook/2005.0/handbook-x86.xml?style=printable&full=1
 (verbose)

        - ensure ALSA and USB 2.0 support during kernel build

- Gentoo emerge the update to gcc 3.4.4 immediately after the 'system' build 
(speculative)

        - http://gentoo-wiki.com/HOWTO_Migrate_to_GCC_3.4

        - else recompile existing key packages that require libstdc++.so.5 
(experience)
                - for i in `find / -type f`; do echo $i ; ldd $i 2>/dev/null | 
grep "not found"; done  # gross, but tells

- Gentoo emerge packages xorg-x11, libusb, tetex (Tex/LaTex), libusb,
hotplug, coldplug, boost, urw-fonts-2.1-r2, alsa-headers(?)

- Gentoo emerge other useful packages such as usbutils, pciutils, xmms,
sox, alsa-utils, etc

- For CVS builds of gnuradio 

        - install base packages per 
http://www.kd7lmo.net/ground_gnuradio_baseline.html
                - but use swig 1.3.23, and not the later 1.3.25 
                - if swig1.3.25 python "ImportError: cannot import name buffer" 
results during gnuradio-core make checks

        - CVS checkout gnuradio code

                http://comsec.com/wiki?HowtoBuildFromCVS 

        - place "$python_path" first in "for" list in all instances of file 
gnuradio-core/config/gr_python.m4
                - else static libpython is found first and configure's test 
program fails to link
                - recall "no dev lib" warning re configure's python development 
lib check

        - make sure PKG_CONFIG_PATH is set and contains
                $HOME/gr/lib/pkgconfig/                         # per 
http://www.kd7lmo.net/ground_gnuradio_baseline.html
                $BUILD/gr-build/gnuradio-core/                  
                $BUILD/gr-build/usrp/

                where $BUILD/gr-build results from the main gnuradio CVS 
checkout 

                        http://comsec.com/wiki?HowtoBuildFromCVS 

        - replace 
                PYTHONPATH="$swigbld:$swigbld/.libs:$swigsrc:$py" 
                with 
                PYTHONPATH="$PYTHONPATH:$swigbld:$swigbld/.libs:$swigsrc:$py" 
                in file 
gr-build/gnuradio-core/src/python/gnuradio/gr/run_tests.in

        - ./for-all-dirs ../buildit 2>&1 | tee make.log  # per 
http://comsec.com/wiki?HowtoBuildFromCVS

- Test by running OTA samples here

        http://www.kd7lmo.net/ground_gnuradio_ota.html

        using python code here

        http://www.kd7lmo.net/ground_gnuradio_ota.html

        (Thanks, KD7LMO!)

Mark




reply via email to

[Prev in Thread] Current Thread [Next in Thread]