Another Building on Mac OS X

Hi,

I am also trying to build on Mac OS X (10.6.8) from source, by first
getting the dependencies worked out from MacPorts.
Although close to work (I think) it still fails for me.
One reason I want to install from source is to get the UHD functionality
directly in GRC, which isn’t available in the GnuRadio version 3.3.0
which MacPorts offer.

I followed a recent instruction found at
https://shannon.ece.ufl.edu:6936/index.php/OS_X_10.6.8_(Snow_Leopard)
However, I needed to translate the setting of shell variables for bash
instead of tcsh.
My paths then seem to be set properly, I believe (but not sure of course
:slight_smile:

This is how it went:

~/gnuradio> ./bootstrap
~/gnuradio> ./configure --prefix=$GR_INSTALL --with-fusb-tech=libusb1
–with-qwt-incdir=/opt/local/include/qwt/
~/gnuradio> make
… (stops with)

make[5]: *** No rule to make target
/opt/local/share/swig/2.0.2/swig.swg', needed bypmt_swig.py’. Stop.
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
~/gnuradio>

That is, for some reason it searches for ‘swig version 2.0.2’, but I
seem to have 2.0.4 installed since
`/opt/local/share/swig/2.0.4/swig.swg’ exists.
How to fix this?
What can the underlying problem be?

FYI, the lines below shows how the “configure” went. That is, all
essential checks passed.
However, I don’t know if the several lines “./configure: line 18387:
test: too many arguments” in the end is a sign of trouble or if it is
acceptable ?

~/gnuradio> ./configure --prefix=$GR_INSTALL --with-fusb-tech=libusb1
–with-qwt-incdir=/opt/local/include/qwt/
… (ending with)

./configure: line 18387: test: too many arguments
./configure: line 18387: test: too many arguments
./configure: line 18387: test: too many arguments
./configure: line 18387: test: too many arguments
./configure: line 18387: test: too many arguments
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config/Makefile
config.status: creating include/Makefile
config.status: creating include/volk/Makefile
config.status: creating lib/Makefile
config.status: creating orc/Makefile
config.status: creating volk.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands

The following architectures will be built:
generic 32 64 3dnow abm mmx sse sse2 orc sse3 ssse3 sse4_a sse4_1
sse4_2


The following GNU Radio components have been successfully configured:

config
gruel
volk
gnuradio-core
gr-digital
gr-audio
gr-vocoder
gr-atsc
gr-noaa
gr-pager
gr-trellis
gr-video-sdl
gr-wxgui
gr-qtgui
gr-utils
gnuradio-examples
grc
gr-uhd
docs

You my now run the make command to build these components.


The following components were skipped either because you asked not
to build them or they didn’t pass configuration checks:

gr-comedi
gr-shd

These components will not be built.

Configured GNU Radio release v3.5.0git-15-ge9f45800 for build.

~/gnuradio> make
make all-recursive
Making all in config
make all-am
make[3]: Nothing to be done for all-am'. Making all in gruel make all-recursive Making all in src Making all in lib make all-recursive Making all in pmt make all-am make[8]: Nothing to be done forall-am’.
Making all in msg
make all-am
make[8]: Nothing to be done for all-am'. make[7]: Nothing to be done forall-am’.
Making all in include
Making all in gruel
make all-am
make[7]: Nothing to be done for all-am'. make[6]: Nothing to be done forall-am’.
Making all in scheme
Making all in gnuradio
make all-am
make[7]: Nothing to be done for all-am'. make[6]: Nothing to be done forall-am’.
Making all in .
make[5]: Nothing to be done for all-am'. Making all in swig make[5]: *** No rule to make target/opt/local/share/swig/2.0.2/swig.swg’, needed by `pmt_swig.py’. Stop.
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
~/gnuradio>

Any help or suggestion appreciated

/ Rickard

Hello Rickard

You could try building using cmake?
if you can do cmake-gui, you should see where to put the path to your
swig
at the bottom, perhaps configuring this explicitly helps?

Best
Paul

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs