Forum: GNU Radio Building from trunk under Ubuntu 8.10?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Rob F. (Guest)
on 2008-12-09 23:12
(Received via mailing list)
Hi Everyone,

I'm having difficulty building under Ubuntu 8.10.  Make ends with these
errors.

Making all in swig
make[5]: Entering directory
`/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/swig'
if /usr/bin/swig -c++ -fvirtual -python -modern -DOMNITHREAD_POSIX=1
-I/usr/include -I/home/frohro/Desktop/gnuradio/omnithread
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/runtime
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/general
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/general
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/gengen
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/gengen
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/filter
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/filter
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/missing
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/reed-solomon
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/viterbi
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/io
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/g72x
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/swig
-I/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/swig
-I/home/frohro/Desktop/gnuradio/gruel/src/include
-I/home/frohro/Desktop/gnuradio/gruel/src/include
-I/usr/include/python2.5 -I.    -MMD -MF gnuradio_swig_py_runtime.Td
-module gnuradio_swig_py_runtime -o gnuradio_swig_py_runtime.cc
gnuradio.i ;\
    then if test linux-gnu = mingw32; \
         then sed 's,\\\\,/,g' <gnuradio_swig_py_runtime.Td
 >gnuradio_swig_py_runtime.d; rm -f gnuradio_swig_py_runtime.Td; \
         else mv -f gnuradio_swig_py_runtime.Td
gnuradio_swig_py_runtime.d; fi \
    else rm -f gnuradio_swig_py_runtime.Td; exit 1; fi
make[5]: *** No rule to make target
`/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/general/gr_ofdm_bpsk_mapper.i',
needed by `gnuradio_swig_py_general.cc'.  Stop.
make[5]: Leaving directory
`/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/swig'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/frohro/Desktop/gnuradio/gnuradio-core/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/frohro/Desktop/gnuradio/gnuradio-core'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/frohro/Desktop/gnuradio'
make: *** [all] Error 2
frohro@engrfrohro6400:~/Desktop/gnuradio$

Any advice?

Thanks,

Rob
Newell J. (Guest)
on 2008-12-09 23:16
(Received via mailing list)
Make sure you follow these guidelines and that you have all the packages
installed that are listed:

http://gnuradio.org/trac/wiki/UbuntuInstall


Take note of the 8.10 section.

--
Newell

http://www.gempillar.com
Before enlightenment: chop wood, carry water
After enlightenment: code, build circuits
Johnathan C. (Guest)
on 2008-12-09 23:18
(Received via mailing list)
On Tue, 2008-12-09 at 12:51 -0800, Rob F. wrote:

> I'm having difficulty building under Ubuntu 8.10.  Make ends with these
> errors.

> make[5]: *** No rule to make target
> `/home/frohro/Desktop/gnuradio/gnuradio-core/src/lib/general/gr_ofdm_bpsk_mapper.i',
> needed by `gnuradio_swig_py_general.cc'.  Stop.

Is this from a fresh checkout of the trunk, or one that was built
before?  This symptom is typical of what happens when the dependencies
from an older build are still lying around after an svn update that
removes a .i file, which happens occasionally.

If this is the case, you can either check out a fresh copy of the trunk,
or do a 'make distclean' from the top directory, then start from
scratch.

-Johnathan
This topic is locked and can not be replied to.