Re: [Discuss-gnuradio] building under FreeBSD

[LRK]

On Thu, Jan 05, 2012 at 09:52:11AM -0600, LRK wrote:
> 
>   The current GnuRadio now builds under FreeBSD using my script. Volk
> is disabled in my script because it did not build and I have not looked
> into that.

Ok, I enable volk again and find this:


g++ -DHAVE_CONFIG_H -I. -I..  -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN -I../inclu
de -I../lib -I/usr/local/include  -I../gen/include -I../include -Dvolk_EXPORTS -
fvisibility=hidden    -g -O2 -nostdinc++ -I/usr/include/c++/4.2.2 -I/usr/include
/c++/4.2.2/ -MT testqa-testqa.o -MD -MP -MF .deps/testqa-testqa.Tpo -c -o testqa
-testqa.o `test -f 'testqa.cc' || echo './'`testqa.cc

qa_utils.h:4:19: error: cstdlib: No such file or directory
qa_utils.h:5:18: error: string: No such file or directory
qa_utils.h:6:18: error: vector: No such file or directory
../include/volk/volk_complex.h:22:19: error: complex: No such file or directory
/usr/local/include/boost/config/select_stdlib_config.hpp:17:19: error: cstddef:
No such file or directory
/usr/local/include/boost/config/no_tr1/utility.hpp:21:21: error: utility: No suc
h file or directory

The errors are due to the code looking for files in /usr/include/c++/4.2.2
which are installed in /usr/include/c++/4.2
FreeBSD uses gcc 4.2.2 in the kernel code and gcc46 installed from the port,
normally only used by some ports.

/usr/include/c++/4.2/tr1/cstdlib
/usr/include/c++/4.2/cstdlib
/usr/local/include/boost/compatibility/cpp_c_headers/cstdlib
/usr/local/lib/gcc46/include/c++/tr1/cstdlib
/usr/local/lib/gcc46/include/c++/cstdlib
/usr/src/contrib/libstdc++/include/tr1/cstdlib
/usr/X11R6/include/boost/compatibility/cpp_c_headers/cstdlib
/usr/X11R6/lib/gcc46/include/c++/tr1/cstdlib
/usr/X11R6/lib/gcc46/include/c++/cstdlib

If I make a link so 4.2.2 is there pointing to the 4.2 directory, it 
compiles, with only 23 warnings about volk.

The autotools build installs and it runs dial_tone.py so it looks better.

The cmake build does not install the gnuradio stuff in the site-packages
directory in PYTHONPATH like autotools did. I found the way to put the
GR_PREFIX in for the other installs but not the PYTHONPATH part.

Onward......


-- 
LRK
gr-user . ovillatx.sytes.net