How to get dqpsk2 block?

GNU Radio
1

It seems I don’t have all DPSK2 blocks installed. Where can i get them?

View this message in context:
http://old.nabble.com/how-to-get-dqpsk2-block--tp29448241p29448241.html
Sent from the GnuRadio mailing list archive at Nabble.com.

2

On Mon, Aug 16, 2010 at 5:39 AM, Thunder87 [email protected]
wrote:

It seems I don’t have all DPSK2 blocks installed. Where can i get them?

You need to be running the code from git; these blocks are not
available through the tarball releases.

If you have the source from git, you should have in
gnuradio-examples/python/digital a version of the benchmarking scripts
with a 2 on them (receive_path2.py, benchmark_tx2.py, etc.).

Tom

3

Somehow managed to install git and get gnuradio source. Now I have a
problem
with source installation. “sudo ./configure” says:

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

gruel
gcell
gnuradio-core
usrp
usrp2
gr-usrp
gr-usrp2
gr-gcell
gr-msdd6000
gr-audio-alsa
gr-audio-jack
gr-audio-oss
gr-audio-osx
gr-audio-portaudio
gr-audio-windows
gr-atsc
gr-comedi
gr-cvsd-vocoder
gr-gpio
gr-gsm-fr-vocoder
gr-noaa
gr-pager
gr-radar-mono
gr-radio-astronomy
gr-trellis
gr-video-sdl
gr-wxgui
gr-qtgui
gr-sounder
gr-utils
gnuradio-examples
grc

These components will not be built.

I have no idea why. It will only install config and docs. Did anyone had
such problem?

Alex

View this message in context:
http://old.nabble.com/how-to-get-dqpsk2-block--tp29448241p29489572.html
Sent from the GnuRadio mailing list archive at Nabble.com.

4

On Fri, Aug 20, 2010 at 12:56:30AM -0700, Thunder87 wrote:

Somehow managed to install git and get gnuradio source. Now I have a problem
with source installation. “sudo ./configure” says:

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

Do you have a C++ compiler installed?

The answer to your question will be in the output from configure.

Eric

5

On Aug 20, 2010, at 12:56 AM, Thunder87 wrote:

Somehow managed to install git and get gnuradio source. Now I have a problem
with source installation. “sudo ./configure” says:

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

gruel
gcell
gnuradio-core
[…]

These components will not be built.

You’re probably missing at least one required library, so it’s not
building any of the important parts of the gnuradio code. Look at the
config.log file that was created by running configure, and find the
first critical component that it decided not to build (probably gruel,
and you’ll most likely find it by searching for the word “building”),
then try to figure out why it didn’t build it. I think it’s ok for gcell
to not be built on most systems, but other components like gruel or
gnuradio-core are critical. Here’s a snippet of my config.log file as an
example:

[…]
configure:21465: checking for byteswap.h
configure:21465: result: no
configure:21548: result: Component gruel passed configuration checks;
building.
configure:21590: checking whether host_cpu is powerpc*
configure:21599: result: no
configure:21606: checking for spu-gcc
configure:21634: result: noconfigure:21667: result: Not building
component gcell.
configure:21937: checking for cblas_sgemm
[…]

Notice that it decided to build gruel, and not to build gcell, and that
it didn’t build gcell because it couldn’t find the spu-gcc compiler. In
your config.log file, it’ll say “…result: Not building component
gruel.”, and the lines (lots of them, including dumps of the test
programs that failed) are what you’ll need to study to determine what’s
missing. Some of the failures are probably innocuous (like my missing
byteswap.h file, I think), and just indicate the sorts of
system-specific variances that the configure script is looking for.
However, there’ll probably be at least one failure to find a critical
library or header file, and that’ll be your first clue about what else
you’ll need to look for and install. You will probably need to repeat
the process many times before all of the critical components will build.

You might also need to pass more arguments to the configure script, if
you determine that it’s not finding something that you’re sure is
installed on your system.

While you’re working your way through finding all of your missing
required libraries, it may be helpful to temporarily add flags such as
“–with-gruel” or “–with-gnuradio-core” to the ./configure invocation
to make the script abort immediately after deciding not to build the
specified component, rather than continuing on and making a zillion more
lines of output for you to sift through. For example, since the critical
gruel component isn’t building on your system, nothing that comes after
it in the configuration script matters until you fix that, and the
“–with-gruel” flag should tell it to give up immediately after deciding
not to build gruel.

By the way, you should only need to use sudo to run the final “make
install” step. None of the configuration and compilation steps before
that should require root privileges.

Good luck!

–
Mark J. Blair, NF6X [email protected]
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.

6

Eric B. wrote:

Do you have a C++ compiler installed?

I do have it.

log repeatedly says:
failed program was /* confdefs.h */

So I guess it’s confdefs.h )) You have any idea what is it?

I googled it. Seems to be a common problem, but I still cant find a
normal
solution or explaination.

View this message in context:
http://old.nabble.com/how-to-get-dqpsk2-block--tp29448241p29497356.html
Sent from the GnuRadio mailing list archive at Nabble.com.

7

Thanks! I’ve started to understand this a bit.

Now it’s like this:

gcell
gr-gcell
gr-audio-jack
gr-audio-osx
gr-audio-portaudio
gr-audio-windows
gr-comedi
gr-video-sdl
grc

These components will not be built.

I wonder if I need gcell and gr-gcell.
Definitely need grc.

Here is a log
http://old.nabble.com/file/p29504085/config.log config.log

I really can’t understand why grc wouldn’t install.

View this message in context:
http://old.nabble.com/how-to-get-dqpsk2-block--tp29448241p29504085.html
Sent from the GnuRadio mailing list archive at Nabble.com.

8

On 22 August 2010 12:22, Thunder87 [email protected] wrote:

gr-audio-windows
gr-comedi
gr-video-sdl
grc

These components will not be built.

I wonder if I need gcell and gr-gcell.

Probably not.

Definitely need grc.

Here is a log
http://old.nabble.com/file/p29504085/config.log config.log

I really can’t understand why grc wouldn’t install.

…
configure:31389: checking for Python >= 2.5
configure:31409: result: yes
configure:31415: checking for Python Cheetah templates >= 2.0.0
configure:31431: result: no
configure:31441: checking for Python lxml wrappers >= 1.3.6
configure:31457: result: no
configure:31467: checking for Python gtk wrappers >= 2.10.0
configure:31487: result: yes
configure:31511: result: Not building component grc.
…

You need Python-LXML and Cheetah Template Engine (as also mentioned in
http://gnuradio.org/redmine/wiki/gnuradio/GNURadioCompanion :wink:

Alex

9

On Aug 21, 2010, at 1:46 AM, Thunder87 wrote:

log repeatedly says:
failed program was /* confdefs.h */

So I guess it’s confdefs.h )) You have any idea what is it?

That “/* confdefs.h */” is just the first line of a temporary C program
generated by the configure script to check whether some header file or
function can be found. It’s not the thing that configure is complaining
that it can’t find. For example, here’s a snippet of my config.log file
where it looks for the header file minix/config.h, and doesn’t find it:

configure:5554: checking minix/config.h presence
configure:5554: /usr/bin/gcc -E -I/opt/local/include
-I/opt/local/include/qwt -I/opt/local/include/qwtplot3d conftest.c
conftest.c:21:26: error: minix/config.h: No such file or directory
configure:5554: $? = 1
configure: failed program was:
| /* confdefs.h /
| #define PACKAGE_NAME “”
| #define PACKAGE_TARNAME “”
| #define PACKAGE_VERSION “”
| #define PACKAGE_STRING “”
| #define PACKAGE_BUGREPORT “”
| #define PACKAGE_URL “”
| #define PACKAGE “gnuradio”
| #define VERSION “v3.3.1git-47-gf6337c62”
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| / end confdefs.h. */
| #include <minix/config.h>
configure:5554: result: no

See, first it says that it’s checking for the presence of
minix/config.h. Next, it prints the command it used to check for that
file (the /usr/bin/gcc line). Next, it prints the output of that
command, where the C compiler said that it couldn’t find minix/config.h.
After that attempted little compilation fails, the configure script
prints out the contents of the temporary little program it created for
the failed test compilation (all of the lines beginning with “|”).
Finally, is prints that the result of its test was “no”.

In this case, it’s not a problem for me that minix/config.h wasn’t
found. It’s just a system-specific variation that the configure script
is testing for. But when a gnuradio component isn’t built, there will
usually be come output that looks like this:

configure:25705: result: no
configure:25707: result: gr-audio-alsa requires package alsa, not found.
configure:25742: result: Not building component gr-audio-alsa.

There was a whole bunch of output right before this from configure’s
tests to see if it could find the “alsa” package, but the part that I
would care about if I wanted to build gr-audio-alsa is just the line
where configure tells me that it’s not building gr-audio-alsa because it
couldn’t find the alsa package… so then I’d go looking for the alsa
package and install it on my system to fix the missing dependency.

At this point, you’re not so much having a gnuradio problem yet…
you’re still learning how to understand the output of the “configure”
script, which is created by the Gnu Autoconf tools. It’s kind of
complicated, but once you get over the learning curve this knowledge
will apply towards working with lots of other open-source stuff, too.

Keep plugging along, and you’ll get there!

–
Mark J. Blair, NF6X [email protected]
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.

10

Hi,

On Aug 22, 2010, at 2:22 PM, Thunder87 wrote:

I wonder if I need gcell and gr-gcell.

I think that’s needed if you want to run GNU Radio on the IBM Cell
Broadband Engine processor, which is used to power the Playstation 3.

http://gnuradio.org/redmine/wiki/gnuradio/PS3FC8Install

The Cell processor on the PS3 has 2 PowerPC processor units, and 7
vector processors (or SPUs, 1 of a total of 8 is disabled to improve
yield). The IBM Cell Blades have chips with all 8 SPUs enabled.

Best regards,

Elvis D.