Release 3.0.1 Unofficial Tarballs

Unofficial tarballs for GNU Radio release 3.0.1 are available at:

http://gnuradio.org/releases/gnuradio/gnuradio-3.0.1.tar.gz
http://gnuradio.org/releases/gnuradio/gr-howto-write-a-block-3.0.1.tar.gz

The release history and changes are available at:

http://gnuradio.org/trac/wiki/Release3.0Branch

Build instructions for GNU Radio 3.0 are at:

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

You may customize your configuration options according to:

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

Many thanks to those who tested the svn repository and release
candidate.

These tarballs will be uploaded to the GNU Project, signed, and made
available on the official download mirrors in the next few days.


Johnathan C., AE6HO
Corgan Enterprises LLC
[email protected]

I’ve tried this version in pkgsrc and I’m getting the following error:

gmake[5]: Entering directory
`/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/src/lib/general’
PYTHONPATH=…/…/…/…/gnuradio-core/src/python srcdir=.
./generate_all.py
Traceback (most recent call last):
File “./generate_all.py”, line 33, in ?
generate_all ()
File “./generate_all.py”, line 28, in generate_all
generate_common.generate ()

File
“/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/src/lib/general/generate_common.py”,
line 82, in generate
expand_h_cc_i (r, s)

File
“/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/src/lib/general/generate_common.py”,
line 68, in expand_h_cc_i
expand_template (d, root + ‘.h.t’)

File
“/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/src/python/build_utils.py”,
line 55, in expand_template
template = open_src (template_filename, ‘r’)

File
“/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/src/python/build_utils.py”,
line 106, in open_src
return open (os.path.join (srcdir, name), mode)
IOError: [Errno 2] No such file or directory: ‘./gr_add_vXX.h.t’
gmake[5]: *** [gr_add_cc.h] Error 1

The configuration string is shown

./configure --enable-doxygen --enable-dot --enable-html-docs
–sysconfdir=/usr/pkg/share/examples --disable-all-components
–enable-gnuradio-core --without-libintl-prefix --prefix=/usr/pkg
–host=i386–netbsdelf --mandir=/usr/pkg/man

builds fine outside pkgsrc (1st pass) but fails in pkgsrc. The same
behavior
is observed after “gmake clean” and building a second time (2nd pass).
Are
these old skeletons of previous versions? What’s gives?

cheerio Berndt

G’day,

ok, the problems appears to be that pkgsrc touches some files in the
gnuradio-core/src/lib/general directory triggering the execution of the
generate_all.py script which imports generate_common.py.

generate_common.py contains a list of files

reg_roots = [
‘gr_add_const_XX’,
‘gr_multiply_const_XX’,
‘gr_add_XX’,
‘gr_sub_XX’,
‘gr_multiply_XX’,
‘gr_divide_XX’,
‘gr_mute_XX’,
‘gr_add_vXX’,
‘gr_multiply_vXX’,
‘gr_add_const_vXX’,
‘gr_multiply_const_vXX’
]

It appars that those ending with _vXX are nolonger part of the
distribution
and may be a leftover from earlier distribution - old skeletons? :slight_smile:

generate_all is also executed after a “gmake clean” since it removes
several
files that are supplied in the tarball, which need to be regenerated,
causing
the same problem.

I removed the files ending in _vXX from the list in generate_common.py
and
successfully built the distribution.

Can someone in the know verify this? Can we get it fixed for the
official
release tarball?

Thanks in advance,

cheerio Berndt

G’day Johnathan,

Ok, they are forming part of the distribution, but I’ve never seen and
obviously never missed them until now.

I didn’t create a pkgsrc distribution for version 3.0 since it had other
problems that needed to be overcome and my working schedule was very
tight at
that time. Hence I’m pretty keen to see this through the door as its
been
awhile since pkgsrc was updated.

I now see that these files are in the SVN repository. Not sure how to
deal
with this as such. Perhaps skip 3.0.1 and release 3.0.2 as the next
official
release?

cheerio Berndt

generate_all is also executed after a “gmake clean” since it removes
several files that are supplied in the tarball, which need to be
regenerated, causing the same problem.

So if we need generate_all to work anyway, probably the files it makes
shouldn’t be in the tarball.

One of the things pkgsrc provokes is that some libtool etc. fixes get
applied (to support platforms pkgsrc runs on that aren’t fixed in the
real libtool, I think, but I’m fuzzy on that), and thus some of the
auto* stuff gets rerun.

But it sounds like once the input files are in the distfile, all will
be ok.

Then the pkgsrc bulk builds on other OSes will be interesting…

On Thu, 2006-11-09 at 18:03 +1030, Berndt Josef W. wrote:

It appars that those ending with _vXX are nolonger part of the distribution
and may be a leftover from earlier distribution - old skeletons? :slight_smile:

Actually, those ending in vXX are part of the source tree and are
supposed to be in the distribution tarball. The bug is not referring to
them in one particular place in the Makefile.am so they get included.

I am the guilty party here–I added those ‘vector’ operations to the
tree as one of the first contributions I ever made to GNU Radio, and
clearly didn’t know what I was doing. It’s a wonder Eric lets me near
the tree sometimes :slight_smile:

But–did pkgsrc ever work for you, say, in the release 3.0 tarballs?
This bug has been there since the CVS days.

Anyway, it’s easy to fix, but we’ve got to huddle and figure out what it
means as far as the release goes. Unfortunately, we already tagged
3.0.1 in the repository off the release branch. We could delete that
tag, and re-tag the release branch after checking in that fix. It would
(almost) be as if this broken 3.0.1 never existed.

Some would call this cheating, others would call it clever.


Johnathan C., AE6HO
Corgan Enterprises LLC
[email protected]