Sir:
If you look in the place where you built gr-osmosdr, you will find a file called install_manifest.txt which contains where it put all the files. The rtlsdr_source_c.xml and osmosdr_source_c.xml (which are files that describe the sources, both of which produce streams of complex numbers, which is what the naming convention means) are how the gnuradio companion knows how to use those sources.
Do a "sudo make uninstall" where you built gr-osmosdr, and then start over with gr-osmosdr. But this time, instead of just running "cmake" with no options, use the command:
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
You "define" (that's what "-D" means) the value "CMAKE_INSTALL_PREFIX" to be /usr. If you don't define it to be something, it will use the default value of "/usr/local"
I have a Web page with partial instructions (it's not intended to be a Linux introduction, although I will do my best to answer specific questions if you have any) and some other stuff on it: http://www.ka8kpn.org/sdr-dongle.html
Oh, and while I'm thinking about it, I really detest mailing lists whose default action on a reply is to write directly to the person to whom you are responding rather than to the list. To me, it is optimizing the atypical case and it makes far more sense to optimize for what everyone nearly always wants to do. That is, it may be technically correct, but it is definitely the wrong thing to do. However, I know I've lost that battle, so I'll not mention it again.
On 01/12/2013 03:24 PM, tokens@myranch.com wrote:
Hi Jonathan,
Please excuse my ignorant comments and questions but I am very much a Linux novice.
I see that there are directories for gr-osmosdr, rtl-sdr, and uhd under home directory. Under usr/local/share/gnuradio/grc/blocks/ I find osmosdr_source_c.xml and rtlsdr_source_c.xml. Directories for gnuradio are under usr/etc and usr/include. I guess this is what you mean by some bits of gr-osmosdr and rtlsdr end up in usr/local. How do I force cmake to install the software into /usr.
Thank you very much.
Regards, Al
-----Original Message----- From: Jonathan Guthrie Sent: Saturday, January 12, 2013 2:18 PM To: tokens@myranch.com Subject: Re: rtl-sdr and gr-osmosdr
On 01/12/2013 09:03 AM, tokens@myranch.com wrote:
I have installed these using the procedures shown in the wiki. I didn’t see any errors during the installation. The packages are on the computer but they are not listed amongst the sources on GNU Radio Companion. If I type in the terminal rtl_test –t I get: Found 1 device(s): 0: ezcap USB 2.0 DVB-T/DAB/FM dongle
Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle usb_open error -3 Failed to open rtlsdr device #0
Any suggestions?
I installed GNURadio as packaged by my distribution, and I did the "cmake; make; sudo make install" that I found, and I got the symptoms you described. The problem I had is that packaged software normally gets installed into /usr and the "cmake, etc" procedure installs it's software into /usr/local. That meant that grc was looking in the wrong place to find the gr-osmosdr bits.
Telling cmake to install the software into /usr fixed my problem. Could it possibly fix yours?
Hi Jonathan,
Jonathan Guthrie wrote:
Sir:
Thanks for the thorough response to a newbie question. I am sure that the original poster and several others by way of the list archive will appreciate it.
I really detest mailing lists whose default action on a reply is to write directly to the person to whom you are responding rather than to the list.
..
it may be technically correct, but it is definitely the wrong thing to do.
It's important to keep in mind that mailing lists are very much a distinct use case for email. Using mailing lists is not like sending direct person-to-person or person-to-group emails.
The reason that so many struggle to appreciate not abusing Reply-To is perhaps that they consider mailing lists to be no different from direct person-to-group emails. It is critical to realize that these two ways of emailing are quite different, even though they accomplish the same thing on the very highest level. (Send one message to many recipients.)
This means that it is critical to be aware of the technology that underpins this communication, in order to use it really successfully.
Needing to understand technology in order to use it is foreign for most people. Needing to understand email is foreign for even more people. It's not particularly fun to understand email, and I don't blame anyone who doesn't want to.
Yet, successfully using mailing lists absolutely requires it.
And by extension, it becomes critical for effortless use of mailing lists to have an email software which can model mailing lists in it's user interface. Because - again - interacting with a mailing list is different from interacting directly with recipients.
I have one reply keybinding for replying to the original author. I have another group reply keybinding for replying to the author and all recipients. I have a third list reply keybinding for replying only to the list(s) that were recipients in the email that I reply to, along with any addresses in Mail-Followup-To headers.
This allows me to always be explicit about what I want, when I reply to an email.
This requires me to know what I want. That is not a burden for me.
It would of course be possible to implement a heuristic for this decision, but it would by definition make some false decisions, and I don't really want to use a tool which is known to not do what I want.
I'll trade the convenience of having only a single reply function which randomly does the wrong thing for having three functions and depending on myself to do the right thing as often as you like.
You mention that you know that not abusing Reply-To is technically correct, perhaps per the "List Reply-To considered harmful" article. If you haven't already read it then I would like to recommend also reading "Reply-To Munging Still Considered Harmful. Really." [1]
Regards
//Peter
[1] http://woozle.org/~neale/papers/reply-to-still-harmful.html
-
Jonathan Guthrie -
Peter Stuge