Re: [Discuss-gnuradio] error in ./configure
You need to have the "dev" packages for the dependencies. Do you have them? Karthik On Thu, Oct 2, 2008 at 6:54 PM, Prasant Misra <[EMAIL PROTECTED]> wrote: > > I downloaded the tarball gnuradio-3.1.3. > > When I run the ./configure, I get the error message: > > configure: error: cannot find usable Python headers > > Please suggest as to what I need to do. > > Thanks. > > Prasant Kumar Misra. > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: Re: Re: [Discuss-gnuradio] Failed to locate boost/shared_ptr.hpp.
Yes, That helped. The make command was successful. On Fri, 03 Oct 2008 Johnathan Corgan wrote : >On Fri, 2008-10-03 at 03:04 +, Prasant Misra wrote: > > > But on make, I get the following: > > > > make all-recursive > > make[1]: Entering directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3' > >Don't use directory names with spaces. > > Prasant Kumar Misra.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: Re: [Discuss-gnuradio] Failed to locate boost/shared_ptr.hpp.
On Fri, 2008-10-03 at 03:04 +, Prasant Misra wrote: > But on make, I get the following: > > make all-recursive > make[1]: Entering directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3' Don't use directory names with spaces. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: Re: [Discuss-gnuradio] Failed to locate boost/shared_ptr.hpp.
Hi, I check the required packages and the configure passed without errors. But on make, I get the following: make all-recursive make[1]: Entering directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3' Making all in config make[2]: Entering directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3/config' Making all in omnithread make[2]: Entering directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3/omnithread' /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DOMNITHREAD_POSIX=1 -DPthreadDraftVersion=10 -I/home/pkmisra/GNU Radio/gnuradio-3.1.3/omnithread -g -O2 -Wall -Woverloaded-virtual -pthread -MT omni_time.lo -MD -MP -MF .deps/omni_time.Tpo -c -o omni_time.lo omni_time.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DOMNITHREAD_POSIX=1 -DPthreadDraftVersion=10 -I/home/pkmisra/GNU Radio/gnuradio-3.1.3/omnithread -g -O2 -Wall -Woverloaded-virtual -pthread -MT omni_time.lo -MD -MP -MF .deps/omni_time.Tpo -c omni_time.cc -fPIC -DPIC -o .libs/omni_time.o g++: Radio/gnuradio-3.1.3/omnithread: No such file or directory make[2]: *** [omni_time.lo] Error 1 make[2]: Leaving directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3/omnithread' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/pkmisra/GNU Radio/gnuradio-3.1.3' make: *** [all] Error 2 Please suggest. On Fri, 03 Oct 2008 George Nychis wrote : > > >Prasant Misra wrote: >> Hi, >> >>How do I fix this problem. >> >>configure: error: Failed to locate boost/shared_ptr.hpp. >> >>I am using Ubuntu 7.0 >> >>Thanks. >> > >You might want to keep all of your build problems in a single thread instead >of creating a new post every time. > >Have you tried looking at the documentation? >http://gnuradio.org/trac/wiki/UbuntuInstall > >- George Prasant Kumar Misra.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Failed to locate boost/shared_ptr.hpp.
Prasant Misra wrote: Hi, How do I fix this problem. configure: error: Failed to locate boost/shared_ptr.hpp. I am using Ubuntu 7.0 Thanks. You might want to keep all of your build problems in a single thread instead of creating a new post every time. Have you tried looking at the documentation? http://gnuradio.org/trac/wiki/UbuntuInstall - George ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Failed to locate boost/shared_ptr.hpp.
Hi, How do I fix this problem. configure: error: Failed to locate boost/shared_ptr.hpp. I am using Ubuntu 7.0 Thanks. Prasant Kumar Misra.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] error in ./configure
On Fri, Oct 03, 2008 at 01:58:33AM -, Prasant Misra wrote: > > Hi, > > I am getting an error while ./configure > configure: error: cannot find usable Python headers > > Also the make command is not recognized. > > Thanks. > Prasant Kumar Misra. Please start by reading the README file in the top directory of the GNU Radio. Then see http://gnuradio.org/trac/wiki/BuildGuide and the system specific instructions that are linked to off of that page. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] error in ./configure
Prasant Misra wrote: Hi, I am getting an error while ./configure configure: error: cannot find usable Python headers Also the make command is not recognized. 'make' will not work until ./configure is successful. But, it's hard to help someone with their environment when we know nothing about it. Operating system? Distribution? - George ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] error in ./configure
Hi, I am getting an error while ./configure configure: error: cannot find usable Python headers Also the make command is not recognized. Thanks. Prasant Kumar Misra.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] error in ./configure
I downloaded the tarball gnuradio-3.1.3. When I run the ./configure, I get the error message: configure: error: cannot find usable Python headers Please suggest as to what I need to do. Thanks. Prasant Kumar Misra.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
ok, it's fixed in 9703... thank you jonathan Dimitris Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International On Fri, Oct 3, 2008 at 01:09, Johnathan Corgan <[EMAIL PROTECTED]> wrote: > On Fri, 2008-10-03 at 01:07 +0200, Dimitris Symeonidis wrote: > >> the -Werror flag comes from gnuradio-core/src/lib/viterbi/Makefile: >> INCLUDES = -Wall -Werror > > I thought we took that out already. Will correct now. > > -- > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
On Fri, 2008-10-03 at 01:07 +0200, Dimitris Symeonidis wrote: > the -Werror flag comes from gnuradio-core/src/lib/viterbi/Makefile: > INCLUDES = -Wall -Werror I thought we took that out already. Will correct now. -- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
the -Werror flag comes from gnuradio-core/src/lib/viterbi/Makefile: INCLUDES = -Wall -Werror Dimitris Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International On Fri, Oct 3, 2008 at 00:07, Josh Blum <[EMAIL PROTECTED]> wrote: > I have this error on ubuntu 8.10. The -Werror flag is there by default, I > never specified it in configure or somewhere else in the system. > > This just happened to change when I upgraded from ubuntu 8.04 > > -Josh > > Eric Blossom wrote: >> >> On Thu, Oct 02, 2008 at 11:21:55PM +0200, Dimitris Symeonidis wrote: >>> >>> i have the latest trunk (9699) >>> g++ is 4.3.1-1ubuntu2 >>> make exits with an error for gnuradio-core/src/lib/viterbi/encode.cc: >>> g++ -DHAVE_CONFIG_H -I. -I../../../.. -Wall -Werror-g -O2 -pthread >>> -pthread -Wall -Woverloaded-virtual -MT encode.o -MD -MP -MF >>> .deps/encode.Tpo -c -o encode.o encode.cc >>> cc1plus: warnings being treated as errors >>> encode.cc: In function 'int main()': >>> encode.cc:50: error: ignoring return value of 'size_t fwrite(const >>> void*, size_t, size_t, FILE*)', declared with attribute >>> warn_unused_result >>> >> >> What was your configure command? >> Any CFLAGS or CXXFLAGS set in your environment? >> >> We don't specify -Werror by default. >> >> Eric >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
I have this error on ubuntu 8.10. The -Werror flag is there by default, I never specified it in configure or somewhere else in the system. This just happened to change when I upgraded from ubuntu 8.04 -Josh Eric Blossom wrote: On Thu, Oct 02, 2008 at 11:21:55PM +0200, Dimitris Symeonidis wrote: i have the latest trunk (9699) g++ is 4.3.1-1ubuntu2 make exits with an error for gnuradio-core/src/lib/viterbi/encode.cc: g++ -DHAVE_CONFIG_H -I. -I../../../.. -Wall -Werror-g -O2 -pthread -pthread -Wall -Woverloaded-virtual -MT encode.o -MD -MP -MF .deps/encode.Tpo -c -o encode.o encode.cc cc1plus: warnings being treated as errors encode.cc: In function 'int main()': encode.cc:50: error: ignoring return value of 'size_t fwrite(const void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result What was your configure command? Any CFLAGS or CXXFLAGS set in your environment? We don't specify -Werror by default. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] powerline PHYs?
On Thu, 2008-10-02 at 14:10 -0500, David Young wrote: > I am curious if/how folks are attaching SDRs to household electrical > outlets for data networking experiments. Are there any kits or > off-the-shelf components that adapt from 120 VAC to a form more suitable > for SDR I/O? > > Dave > There is a link in the gnuradio archives http://lists.gnu.org/archive/html/discuss-gnuradio/2008-08/msg00280.html ... but I am not sure this should be encouraged. jim ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
On Thu, Oct 02, 2008 at 11:21:55PM +0200, Dimitris Symeonidis wrote: > i have the latest trunk (9699) > g++ is 4.3.1-1ubuntu2 > make exits with an error for gnuradio-core/src/lib/viterbi/encode.cc: > g++ -DHAVE_CONFIG_H -I. -I../../../.. -Wall -Werror-g -O2 -pthread > -pthread -Wall -Woverloaded-virtual -MT encode.o -MD -MP -MF > .deps/encode.Tpo -c -o encode.o encode.cc > cc1plus: warnings being treated as errors > encode.cc: In function 'int main()': > encode.cc:50: error: ignoring return value of 'size_t fwrite(const > void*, size_t, size_t, FILE*)', declared with attribute > warn_unused_result > What was your configure command? Any CFLAGS or CXXFLAGS set in your environment? We don't specify -Werror by default. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] compile error on gnuradio-core/src/lib/viterbi/encode.cc
i have the latest trunk (9699) g++ is 4.3.1-1ubuntu2 make exits with an error for gnuradio-core/src/lib/viterbi/encode.cc: g++ -DHAVE_CONFIG_H -I. -I../../../.. -Wall -Werror-g -O2 -pthread -pthread -Wall -Woverloaded-virtual -MT encode.o -MD -MP -MF .deps/encode.Tpo -c -o encode.o encode.cc cc1plus: warnings being treated as errors encode.cc: In function 'int main()': encode.cc:50: error: ignoring return value of 'size_t fwrite(const void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result Dimitris Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] minor remarks on installation instructions under ubuntu
On Thu, 2008-10-02 at 22:08 +0200, Dimitris Symeonidis wrote: > What does the list think? Should I make the changes on the wiki page? This sounds fine. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] minor remarks on installation instructions under ubuntu
Some minor remarks on the Gnuradio install instructions for Ubuntu on the wiki: http://gnuradio.org/trac/wiki/UbuntuInstall 1) libasound2-dev is automatically installed by libsdl1.2-dev, so could we remove it? Not that it hurts to explicitely ask for it to be installed, but it's superfluous... 2) Intrepid includes both libboost-dev (which is boost version 1.34.1) and libboost1.35-dev. The second one will also let you build the latest trunk of gnuradio... Should we ask the users to install this one instead? 3) python-numpy-ext is a transitional package and should be replaced by python-numpy What does the list think? Should I make the changes on the wiki page? I also want to draw everyone's attention to the fact that users upgrading to Intrepid from earlier versions of Ubuntu will lose the ability to compile the USRP code, due to the split of sdcc into sdcc and sdcc-nf. Dimitris Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] powerline PHYs?
I am curious if/how folks are attaching SDRs to household electrical outlets for data networking experiments. Are there any kits or off-the-shelf components that adapt from 120 VAC to a form more suitable for SDR I/O? Dave -- David Young OJC Technologies [EMAIL PROTECTED] Urbana, IL * (217) 278-3933 ext 24 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How can I check usrp.sink_c
On Thu, Oct 02, 2008 at 09:25:08AM -0700, Dan Halperin wrote: > On Oct 2, 2008, at 7:34 AM, kaleem ahmad wrote: > > > Hi, > > > > I want to transmit some data using usrp.sink_c and immediately after > > the > > data is sent I want to start receiver mode, but my problem is if I > > do like > > this: > > > > Send using 'usrp.sink_c' > > start receive mode > > > > My USRP immediately goes into receive mode and the data sent is not > > successful, so I want to do something like following: > > > > Send using 'usrp.sink_c' > > check 'usrp.sink_c' if the data is sent then > > start receive mode > > There is an automatic switching between transmit and receive modes > that does what you want -- whenever there is something being > transmitted, it disables the receive chain, and switches back once > that buffer is empty. Look through the examples for flow graphs with > both transmit and receive chains. It's called something like auto_tr. > > -Dan This is all good. Kaleem, I suggest that you take a look at gnuradio-examples/python/digital/tunnel.py. The MAC that it implements is terrible, but it does show how to have both the Tx and Rx running without having to reconfigure anything. Basically there are two disjoint pipelines: network --> -> usrp.sink_c usrp.source_c --> --> network They both run at the same time and use the auto_tr feature. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How can I check usrp.sink_c
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 2, 2008, at 7:34 AM, kaleem ahmad wrote: Hi, I want to transmit some data using usrp.sink_c and immediately after the data is sent I want to start receiver mode, but my problem is if I do like this: Send using 'usrp.sink_c' start receive mode My USRP immediately goes into receive mode and the data sent is not successful, so I want to do something like following: Send using 'usrp.sink_c' check 'usrp.sink_c' if the data is sent then start receive mode There is an automatic switching between transmit and receive modes that does what you want -- whenever there is something being transmitted, it disables the receive chain, and switches back once that buffer is empty. Look through the examples for flow graphs with both transmit and receive chains. It's called something like auto_tr. - -Dan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkjk9eQACgkQy9GYuuMoUJ5VnACbBRdFmIQcD0JF5hQThV6Z5oe7 tksAoICpSompAsP4d5Wq6TytrLqNyX6+ =AWGx -END PGP SIGNATURE- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] How can I check usrp.sink_c
Hi, I want to transmit some data using usrp.sink_c and immediately after the data is sent I want to start receiver mode, but my problem is if I do like this: Send using 'usrp.sink_c' start receive mode My USRP immediately goes into receive mode and the data sent is not successful, so I want to do something like following: Send using 'usrp.sink_c' check 'usrp.sink_c' if the data is sent then start receive mode But I dont know how can I check that data is successfully sent or it is still on the way..Any suggestions I am using USRP + RFX2400 + SUSI Best Regards Kaleem Ahmad -- View this message in context: http://www.nabble.com/How-can-I-check-usrp.sink_c-tp19780504p19780504.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Dynamically changing parameters of a block
Any suggestions!! kaleem ahmad wrote: > > Hi Eric, > > Two nodes, each consists of one USRP and an RFX2400, are involved, one as > a Master(Transmit ... receive echoed version...Transmit new packet and so > on) and the other USRP is Slave (Receive...echo back the received packet). > I am creating 1 usrp source (for transmitting) and 1 usrp sink (for > receiving) for each node. > > I dont understand "You should be creating 1 each for each USRP and keep > them open the > entire time." > > How can I keep both source and sink open all the time without using > disconnect/disconnect_all. Because when I am transmitting my source is a > file and my sink is usrp. At same USRP node when I am receiving my source > is usrp and my sink is a file. My problem is how can I construct a graph > which either keep both of these things open at a time or dynamically > connect and disconnect them. > > Can you suggest me an example flow graph, or e.g can you comment that > something like following is correct way to handle it: > > + > while(1): >send() >receive() >delay(500ms) > --- > send(fg): > fg.connect(file_source, frammer, NRZ, modulation, gain, usrp) > - > receive(fg): > fg.disconnect_all() > fg.connect(usrp, filter, de_modulation, correlation, file_sink) > wait_for_timeout() > fg.disconnect_all() > ++ > > It is just an example flowgraph and soesnt matter if the correct blocks > are used, but the thing which I want to know is the order of connect() and > disconnect_all(), is it possible to have like this and will it work with > such delays. > > Best Regards > > Kaleem Ahmad > > Eric Blossom wrote: >> >> On Tue, Sep 30, 2008 at 02:09:47AM -0700, kaleem ahmad wrote: >>> >>> Any suggestions!!! >> >> How many usrps are involved in this? >> How many usrp sinks and sources are you creating? >> You should be creating 1 each for each USRP and keep them open the >> entire time. >> >> Eric >> >> >>> kaleem ahmad wrote: >>> > >>> > Hi Eric and others, >>> > >>> > I also have a similar problem, but it is not limited to 'gain >>> control', >>> > Actually I want to implement an echo back or ping pong transmission >>> > system. >>> > >>> > First I implemented two separate transmitt and receive flow graphs in >>> two >>> > separate transmit(), and receive() functions as mentioned in the >>> > following: >>> > >>> > Master Transceiver: >>> > >>> > Transmit()Transmitt one data packet >>> > Receive() Wait in receive for the echoed back packet >>> or >>> > timeout >>> > >>> > Slave Transceiver: >>> > >>> > if (Receive()): Always wait in receive >>> > Transmit()Transmitt back the received data >>> packet >>> > >>> > But in this method I get an error 'cant open usb devicecant open >>> USRP >>> > 0/1' >>> > >>> > Then I found flowgraph.disconnect() method and thought that I should >>> > implement a single flowgraph which can dynamically connect different >>> > blocks to transmit and then disconnect and connect with receive blocks >>> and >>> > so on... >>> > >>> > Is it possible and is there any example code which doing something >>> like >>> > this or otherwise can you please suggest me some way to do this. >>> > >>> > Thanks >>> > >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > > -- View this message in context: http://www.nabble.com/Dynamically-changing-parameters-of-a-block-tp19698798p19775571.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
