I am trying to get from the repository gnuradio v 2.8. Since I don’t
know
dates or revision numbers, I download revisions and check them out.
I have an either or question. Does anyone know of a stable 2.8 revision
for
me to download? Failing that, i would appreciate it if someone could
tell
me a way to get gnuradio’s version # from the source tree (without
building
it).
TIA,
Nikos
On Fri, Jan 17, 2014 at 1:30 PM, Nikos B.
[email protected] wrote:
Nikos
I think you might be confused. You don’t really mean 2.8, do you? I
would imagine you’re looking for 3.8, which doesn’t actually exist
yet. We’re currently on 3.7.2.1.
You can look in git for the version releases by using “git tag” to see
a list of tags that correspond to the version. Wen you have a version
of GNU Radio, you can look at the root CMakeLists.txt file for the
“VERSiON_INFO_MAJOR_VERSION” and other version variables set up here.
Tom
Sorry, I actually need 2.8. That’s my problem. Repository has releases
since 2006, so it should have 2.8 as well. It is paramount to get that
version. Recent versions won’t work with my other programs. 
On Sat, Jan 18, 2014 at 12:29 AM, Tom R. [email protected] wrote:
Tom
OK. How about you tell me how to find the gnuradio version number from
the
source tree, once I download it (without actually building it)? There
must
be a way.
I believe that old of a revision was before we started using git, so
that
commit (was in SVN) actually does not exist. It’s probably easier to
port
whatever application to the modern API and then you don’t have to
personally maintain 2 old pieces of code.
On Friday, January 17, 2014, Nikos B. [email protected]
On Fri, Jan 17, 2014 at 5:23 PM, Nikos B.
[email protected] wrote:
Sorry, I actually need 2.8. That’s my problem. Repository has releases since
2006, so it should have 2.8 as well. It is paramount to get that version.
Recent versions won’t work with my other programs.
Sorry, no. Absolutely no support for a version that old.
Tom
Just FYI, the first tag might be 3.3, but the git repo starts off as
revision 2.8svn. It moved to 3.0 at commit
9702787a5c9f8ae38c5a34cc957a2ddd3ed0ff5d. So you might get what you’re
looking for by checking out commits prior to that, but as those commits
are
eight years old now it’s probably going to be a real nightmare trying to
get it compiled and working on a modern system.
–n
On Sat, Jan 18, 2014 at 1:26 AM, West, Nathan
[email protected]wrote:
I believe that old of a revision was before we started using git, so that
commit (was in SVN) actually does not exist. It’s probably easier to port
whatever application to the modern API and then you don’t have to
personally maintain 2 old pieces of code.
Unfortunately, it is not my code. It is third party, and I cannot do
anything about it. 
On 01/17/2014 06:17 PM, Nikos B. wrote:
> Sorry, I actually need 2.8. That's my problem. Repository has releases since > 2006, so it should have 2.8 as well. It is paramount to get that version. > Recent versions won't work with my other programs. :-( Sorry, no. Absolutely no support for a version that old. Tom
OK. How about you tell me how to find the gnuradio version number from
the source tree, once I download it (without actually building it)?
There must be a way.
I think Tom already told you how to do this, but this is what what “git
tag”.
Here’s what it produces:
v3.3.0
v3.3.0-rc0
v3.3.0-rc1
v3.3.0-rc2
v3.3.0-rc3
v3.3.1
v3.3.1git
v3.4.0
v3.4.0git
v3.4.1
v3.4.1git
v3.4.2
v3.4.2git
v3.4git
v3.5.0
v3.5.0git
v3.5.0rc0
v3.5.1
v3.5.2
v3.5.2.1
v3.5.3
v3.5.3.1
v3.5.3.2
v3.5.3git
v3.6.0
v3.6.1
v3.6.2
v3.6.3
v3.6.3.1
v3.6.3rc0
v3.6.4
v3.6.4.1
v3.6.4.2
v3.6.4git
v3.6.5
v3.6.5.1
v3.7.0
v3.7.0.1
v3.7.0rc0
v3.7.1
v3.7.1.1
v3.7.2
v3.7.2.1
You’ll notice that the repo starts at v3.3.0
At some point in Gnu Radio’s past, we switched from subversion to git.
Not sure if the subversion archives are still around.
Gnu Radio 2.8 is so old that many of the folks currently supporting Gnu
Radio weren’t even around when it was released. My suggestion would
be to port whatever code you have to 3.6.5 or 3.7.2.
On Sat, Jan 18, 2014 at 1:31 AM, Marcus D. Leech [email protected]
wrote:
Sorry, I actually need 2.8. That’s my problem. Repository has releases
v3.4.1git
v3.5.3.1
v3.6.4.2
Sorry, can’t do. As i mentioned before, it is not my code to port :-(.
Subversion is still around and good. I have downloaded the first
revision
from 2006. However, I can’t tell which version is and it has a bug, so
it
cannot build. Thanx for all your help, i still hope that someone will
remember smt to help me find it. It is really unfortunate that you don’t
keep versions in your sources, like most opensource does. In the future
a
new versioning system will come out, and you will have the same exact
problem with git.
[…snipped…]
On Sat, Jan 18, 2014 at 12:05 AM, Tom R. [email protected] wrote:
a way to get gnuradio’s version # from the source tree (without building
a list of tags that correspond to the version. Wen you have a version
of GNU Radio, you can look at the root CMakeLists.txt file for the
“VERSiON_INFO_MAJOR_VERSION” and other version variables set up here.Tom
I have grepped through all sources, but didn’t check CMakeLists. This
might
just do it. Thanks 
On Sat, Jan 18, 2014 at 1:35 AM, Nick F. [email protected]
wrote:
Just FYI, the first tag might be 3.3, but the git repo starts off as
revision 2.8svn. It moved to 3.0 at commit
9702787a5c9f8ae38c5a34cc957a2ddd3ed0ff5d. So you might get what you’re
looking for by checking out commits prior to that, but as those commits are
eight years old now it’s probably going to be a real nightmare trying to
get it compiled and working on a modern system.–n
Thanks. This is excellent. It is my understanding that gnuradio had a
mjor
change starting with 3.0. Last commits before then, should still be in
the
old format
On Sat, Jan 18, 2014 at 8:58 AM, Marcus D. Leech [email protected]
wrote:
new versioning system will come out, and you will have the same exact
problem with git.So, just to clarify. The code in question is closed-source, and you
can’t get the source code to modify it?If it’s directly linked with Gnu Radio libraries, that’s a bit of a legal
problem…i could make 2 unknown (to me) projects talk to each other, and then
develop my project as well, but I am a single developer, and just want
to
demonstrate feasibility of approach. My final project will have my own
code.
BR,
Nikos
On 01/18/2014 01:49 AM, Nikos B. wrote:
So, just to clarify. The code in question is closed-source, and you
can’t get the source code to modify it?
If it’s directly linked with Gnu Radio libraries, that’s a bit of a
legal problem…
On Sat, Jan 18, 2014 at 9:48 AM, Marcus M. [email protected]
wrote:
And that’s exactly where your problems start: That build system was
including not only libraries, but hard-to-tame things like autoconfigureyou’ll need to future-proof it by porting it to GR 3.7.
Greetings,
MarcusHi Marcus,
Thnx for the advise. I will have to try. Maybe I will prove wrong. I
will
know within the next week.
I am an opensource guru, having contribute to several projects, and am
aware of the license limitations.
2.8 is more recent than 2006. 2006 is the earliest year in the
repository.
I have tried building the earliest
revision in your repository, and it did fine, until it failed due to a
missing “Makefile.in” file. No failed library
dependencies, since most software checks for versions >= a given level.
It
is a good thing that
opensource is mostly backwards-compatible
As I mentioned to the other Marcus, that’s my ultimate goal. I need the
2.8
version to understand better both
gnuradio and the other application. Then I will write my code for the
final
product.
My product is classified, so i am sorry if I cannot be more open with
it.
My clients are the police and the military.
I would like to thank each one in this group. Not only there was a huge
response for an outdated version, well OK,
just for finding it, but also while I asked for onoy 1 of 2 options in
locating it, I was offered both
Please hear my advise. Developers should support the “gnuradio -v”
option
and use an include file to do it.
In a few years git will be superseded by another versioning system. The
only way to ensure that versions are
preserved across any such migration, is to have it embedded in the
sources
ty
Nikos
Just to update you.
It seems that the repository has gnuradio >= 3.0. It is impossible to
tell
in those old revisions the version number (no cmake, no git tags) but
getting the earliest revision from 3/2006, I came across a Changelog
with
entries since 7/2006! Go figure! The changeover to 3.0 given by Nick was
from 6/2006
It seems I cannot use anything from your repository.
Thanks again for your help 
Nikos
[…snipped…]
On Sat, Jan 18, 2014 at 8:57 AM, Nikos B.
[email protected] wrote:
Please hear my advise. Developers should support the “gnuradio -v” option
and use an include file to do it.
In a few years git will be superseded by another versioning system. The only
way to ensure that versions are
preserved across any such migration, is to have it embedded in the sources
ty
Nikos
You mean like:
$ gnuradio-config-info -v
v3.7.2.1-120-g0c895a71
Which of course requires you to have compiled GNU Radio, and you were
asking earlier about knowing the version when it wasn’t already
compiled. My answer before is the same as it is now:
$ grep VERSION_INFO CMakeLists.txt
set(VERSION_INFO_MAJOR_VERSION 3)
set(VERSION_INFO_API_COMPAT 7)
set(VERSION_INFO_MINOR_VERSION 3)
set(VERSION_INFO_MAINT_VERSION git)
Tom
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Niklos,
you’re on a wrong track; when I had my first contact with GR, the
project was still using Autoconfigure/Automake for building. CMakeList
ist part of the CMake-based build system that GR adapted later on in the
3.4 development process (if I remember correctly).
And that’s exactly where your problems start: That build system was
complicated, and not very flexible. Thus, it’s not very easy to fix
dependencies if for example libraries used by GR changed their file
naming structure etc.
This wouldn’t be a big problem if there would only have been a very few
changes in the open source software world; but remember, we are talking
about the world of 2006! So in order to get GR to compile you not only
have to get the right source code version of GR, you need to get the
correct development and built version of all the required libraries to
be available for your system. This is not very likely to be the case
anymore! Lots of things simply have changed since then - possibly
including not only libraries, but hard-to-tame things like autoconfigure
too.
To put summarize your options:
If the 2006 legacy application code is complicated, large and of high
importance to eg test the functionality, then set up a VM running a
Debian from back-in-the-days and try to build and run your application
there. Obviously, as you seem to be hesitant to port the application to
a modern GR (and from an application point of view, this is equal to not
porting it to a halfway-recent operation system) it will be
unmaintainable; and that is a bad thing ™.
If you just want to understand what’s happening inside your legacy
application, well, it might be easier to just read the source code (and
maybe port it to 3.7.2 in the process, which is easier than you might
expect due to tools that ease the pain of having to write a lot of
boilerplate code).
If your business / research really depends on that legacy code:
Get the source code. You must be able to get it from your supplier,
otherwise as Marcus (the other Marcus) already said, he’d be in a bit of
a legal problem. And as said before, since if it is critical to you,
you’ll need to future-proof it by porting it to GR 3.7.
Greetings,
Marcus
On 18.01.2014 07:53, Nikos B. wrote:
I have an either or question. Does anyone know of a stable 2.8
I think you might be confused. You don’t really mean 2.8, do you?I have grepped through all sources, but didn’t check CMakeLists.
This might just do it. Thanks_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS2jGwAAoJEAFxB7BbsDrLUK8IAIegjKtJJVSnMJy4jFxJB7N5
C7Hs01skGoJiDz83c4aJAL6SF0ozEp2kn2wsToUMPWQ2kARudM8Mfb6VVke9QTg3
Ur/ztpSKNtGAZufQYNOE7FQgX9HeGMuHVgLP0c4LOpDPU9VA9jeiV0NESHfoi6aC
eU0wXdH+mlTgWhmQElLBQzwfo5m3mq29RHFAvQYKC1kue7JF5jKzHbD6KP7f+Ukj
bEMUb6cgb1k2kqL+6KgShzc1NfCzOb0BF89HAp9lXIH79zKDYudENvGgFU/Z8O+N
vWanreBeXnyGMNaPPZ276luzGiu0caufQfSno9GvrISlhuFJJORfJOTEjxlwuqw=
=gbX4
-----END PGP SIGNATURE-----
On Sat, Jan 18, 2014 at 6:39 PM, Tom R. [email protected] wrote:
Which of course requires you to have compiled GNU Radio, and you were
The revisions that I was interested, don’t use cmake.
On Sat, Jan 18, 2014 at 5:37 PM, Nikos B.
[email protected] wrote:
Just to update you.
It seems that the repository has gnuradio >= 3.0. It is impossible to tell
in those old revisions the version number (no cmake, no git tags) but
getting the earliest revision from 3/2006, I came across a Changelog with
entries since 7/2006! Go figure! The changeover to 3.0 given by Nick was
from 6/2006It seems I cannot use anything from your repository.
How about:
http://gnu.mirror.iweb.com/gnuradio/old/
or probably any other GNU FTP mirror:
http://www.gnu.org/prep/ftp.html
Alex
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs