Re: [Discuss-gnuradio] Unable to compile under MinGW in a directoryoutside MSYS
On 11/6/2010 2:38 AM, Don Ward wrote: Jimmy Richardson wrote: I got latest MinGW installed and I'm trying to compile latest GNURadio based on the steps from http://gnuradio.org/redmine/wiki/gnuradio/MingwInstallMain, everything works if I put the gnuradio source files under /usr/src/gnuradio, however if I run ./bootstrap and ./configure from outside MSYS directory system, say E:\gnuradio (i.e. change directory to /e/gnuradio inside MSYS) and run ./bootstrap and ./configure, then make, I got error: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:75:3: error: 'mkdir' was not declared in this scope make[5]: *** [test_gruel.o] Error 1 Is there a ./configure flag I should use in this case? My guess is that this is due to a recent change in gruel/src/lib/test_gruel.cc. Try adding the line #include unistd.h immediately after the line #include sys/stat.h Please let us know if this works. It did get rid of the original error, but I got a new one now: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:76:3: error: too many arguments to function 'int mkdir(const char* )' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here test_gruel.cc:77:3: error: too many arguments to function 'int mkdir(const char* )' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here make[5]: *** [test_gruel.o] Error 1 I can see the following in config.log: configure:19611: checking whether mkdir accepts only one arg configure:19628: gcc -c -DWINVER=0x0501 -I/usr/local/include conftest.c 5 configure:19628: $? = 0 configure:19629: result: yes and in the end: ## --- ## ## confdefs.h. ## ## --- ## /* 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 #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 #define __EXTENSIONS__ 1 #define _ALL_SOURCE 1 #define _GNU_SOURCE 1 #define _POSIX_PTHREAD_SEMANTICS 1 #define _TANDEM_SOURCE 1 #define CXX_HAS_STD_ISNAN /**/ #define LT_OBJDIR .libs/ #define HAVE_PYTHON_H 1 #define STDC_HEADERS 1 #define HAVE_FCNTL_H 1 #define HAVE_LIMITS_H 1 #define HAVE_STRINGS_H 1 #define HAVE_TIME_H 1 #define HAVE_SYS_TIME_H 1 #define HAVE_UNISTD_H 1 #define HAVE_SYS_TYPES_H 1 #define HAVE_STDINT_H 1 #define HAVE_SCHED_H 1 #define HAVE_SIGNAL_H 1 #define HAVE_MALLOC_H 1 #define HAVE_WINDOWS_H 1 #define HAVE_SYS_TYPES_H 1 #define TIME_WITH_SYS_TIME 1 #define HAVE_ALLOCA 1 #define ALIGNED_MALLOC 0 #define HAVE_VPRINTF 1 #define HAVE_STRCSPN 1 #define HAVE_STRERROR 1 #define HAVE_STRSPN 1 #define HAVE_GETPAGESIZE 1 #define HAVE_SNPRINTF 1 #define HAVE_GETTIMEOFDAY 1 #define HAVE_MODF 1 #define HAVE_SQRT 1 #define HAVE_SINF 1 #define HAVE_COSF 1 #define HAVE_TRUNC 1 #define HAVE_LOG2 1 #define HAVE_CREATEFILEMAPPING 1 #define HAVE_SYS_TYPES_H 1 #define HAVE_FCNTL_H 1 #define HAVE_IO_H 1 #define HAVE_WINDOWS_H 1 #define HAVE_WINIOCTL_H 1 #define HAVE_WINBASE_H 1 #define HAVE_GETOPT 1 #define HAVE_USLEEP 1 #define HAVE_GETTIMEOFDAY 1 #define HAVE_RAND 1 #define HAVE_SRAND 1 #define HAVE_STRUCT_TIMEZONE 1 #define HAVE_SSIZE_T 1 #define HAVE_GETOPT 1 #define HAVE_USLEEP 1 #define HAVE_GETTIMEOFDAY 1 #define HAVE_SSLEEP 1 #define MKDIR_TAKES_ONE_ARG /**/ #define HAVE_BOOST 1 #define HAVE_PTHREAD 1 #define HAVE_BOOST_THREAD 1 #define HAVE_BOOST_DATE_TIME 1 #define HAVE_BOOST_PROGRAM_OPTIONS 1 #define HAVE_CBLAS 1 #define HAVE_FCNTL_H 1 #define HAVE_SYS_TIME_H 1 #define HAVE_UNISTD_H 1 #define HAVE_DECL_GETENV 1 #define mkstemp rpl_mkstemp #define HAVE_STDINT_H 1 #define HAVE_GETTIMEOFDAY 1 #define MKDIR_TAKES_ONE_ARG /**/ #define HAVE_SNPRINTF 1 #define HAVE_LIBWINMM 1 -- Don W. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Unable to compile under MinGW in a directoryoutside MSYS
Jimmy Richardson wrote: On 11/6/2010 2:38 AM, Don Ward wrote: Jimmy Richardson wrote: I got latest MinGW installed and I'm trying to compile latest GNURadio based on the steps from http://gnuradio.org/redmine/wiki/gnuradio/MingwInstallMain, everything works if I put the gnuradio source files under /usr/src/gnuradio, however if I run ./bootstrap and ./configure from outside MSYS directory system, say E:\gnuradio (i.e. change directory to /e/gnuradio inside MSYS) and run ./bootstrap and ./configure, then make, I got error: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:75:3: error: 'mkdir' was not declared in this scope make[5]: *** [test_gruel.o] Error 1 Is there a ./configure flag I should use in this case? My guess is that this is due to a recent change in gruel/src/lib/test_gruel.cc. Try adding the line #include unistd.h immediately after the line #include sys/stat.h Please let us know if this works. It did get rid of the original error, but I got a new one now: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:76:3: error: too many arguments to function 'int mkdir(const char*)' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here test_gruel.cc:77:3: error: too many arguments to function 'int mkdir(const char* )' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here make[5]: *** [test_gruel.o] Error 1 I can see the following in config.log: configure:19611: checking whether mkdir accepts only one arg configure:19628: gcc -c -DWINVER=0x0501 -I/usr/local/include conftest.c 5 configure:19628: $? = 0 configure:19629: result: yes Aha! In gruel/src/lib/test_gruel.cc, try adding the line #include config.h before the line #include cppunit/TextTestRunner.h Let us know if that fixes it. Thanks, -- Don W. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP BasicRX read_io() from pins
Hi all, I want to read an input from BasicRX pins using read_io() I could not find a document how to do this in python. An example would be great thank you in advance. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Unable to compile under MinGW in a directoryoutside MSYS
On 11/6/2010 8:16 PM, Don Ward wrote: Jimmy Richardson wrote: On 11/6/2010 2:38 AM, Don Ward wrote: Jimmy Richardson wrote: I got latest MinGW installed and I'm trying to compile latest GNURadio based on the steps from http://gnuradio.org/redmine/wiki/gnuradio/MingwInstallMain, everything works if I put the gnuradio source files under /usr/src/gnuradio, however if I run ./bootstrap and ./configure from outside MSYS directory system, say E:\gnuradio (i.e. change directory to /e/gnuradio inside MSYS) and run ./bootstrap and ./configure, then make, I got error: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:75:3: error: 'mkdir' was not declared in this scope make[5]: *** [test_gruel.o] Error 1 Is there a ./configure flag I should use in this case? My guess is that this is due to a recent change in gruel/src/lib/test_gruel.cc. Try adding the line #include unistd.h immediately after the line #include sys/stat.h Please let us know if this works. It did get rid of the original error, but I got a new one now: test_gruel.cc: In function 'void ensure_unittest_path(const char*, const char*)' : test_gruel.cc:76:3: error: too many arguments to function 'int mkdir(const char*)' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here test_gruel.cc:77:3: error: too many arguments to function 'int mkdir(const char* )' c:\mingw\bin\../lib/gcc/mingw32/4.5.0/../../../../include/io.h:302:3 7: note: declared here make[5]: *** [test_gruel.o] Error 1 I can see the following in config.log: configure:19611: checking whether mkdir accepts only one arg configure:19628: gcc -c -DWINVER=0x0501 -I/usr/local/include conftest.c 5 configure:19628: $? = 0 configure:19629: result: yes Aha! In gruel/src/lib/test_gruel.cc, try adding the line #include config.h before the line #include cppunit/TextTestRunner.h Let us know if that fixes it. Yes, this change fixed the error, make works now, thanks! Thanks, -- Don W. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP BasicRX read_io() from pins
On Sat, Nov 06, 2010 at 11:11:51AM -0400, Burak TUYSUZ wrote: Hi all, I want to read an input from BasicRX pins using read_io() I could not find a document how to do this in python. An example would be great thank you in advance. pins = u.read_io(0) # 0 - side A; 1 - side B Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP BasicRX read_io() from pins
Thanks Eric, Is there a pps input application/example done with this on USRP1 probably using a counter in python. I would like it to count the pulses coming from a source and according to that start collecting data. I would appreciate if you could explain this a little bit. Thank you On Sat, Nov 6, 2010 at 12:32 PM, Eric Blossom e...@comsec.com wrote: On Sat, Nov 06, 2010 at 11:11:51AM -0400, Burak TUYSUZ wrote: Hi all, I want to read an input from BasicRX pins using read_io() I could not find a document how to do this in python. An example would be great thank you in advance. pins = u.read_io(0) # 0 - side A; 1 - side B Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP BasicRX read_io() from pins
On Sat, Nov 06, 2010 at 12:43:28PM -0400, Burak TUYSUZ wrote: Thanks Eric, Is there a pps input application/example done with this on USRP1 probably using a counter in python. Not that I know of. I would like it to count the pulses coming from a source and according to that start collecting data. I would appreciate if you could explain this a little bit. Thank you On Sat, Nov 6, 2010 at 12:32 PM, Eric Blossom e...@comsec.com wrote: On Sat, Nov 06, 2010 at 11:11:51AM -0400, Burak TUYSUZ wrote: Hi all, I want to read an input from BasicRX pins using read_io() I could not find a document how to do this in python. An example would be great thank you in advance. pins = u.read_io(0) # 0 - side A; 1 - side B Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP BasicRX read_io() from pins
Do you think that it will work or should I use verilog for this purpose? Actually I did something in verilog but I guess when I stop collecting data some of the data waiting in the buffers, so that is why I wanted to learn if it is easier to do in python. Thank you On Sat, Nov 6, 2010 at 12:48 PM, Eric Blossom e...@comsec.com wrote: On Sat, Nov 06, 2010 at 12:43:28PM -0400, Burak TUYSUZ wrote: Thanks Eric, Is there a pps input application/example done with this on USRP1 probably using a counter in python. Not that I know of. I would like it to count the pulses coming from a source and according to that start collecting data. I would appreciate if you could explain this a little bit. Thank you On Sat, Nov 6, 2010 at 12:32 PM, Eric Blossom e...@comsec.com wrote: On Sat, Nov 06, 2010 at 11:11:51AM -0400, Burak TUYSUZ wrote: Hi all, I want to read an input from BasicRX pins using read_io() I could not find a document how to do this in python. An example would be great thank you in advance. pins = u.read_io(0) # 0 - side A; 1 - side B Eric -- Burak TUYSUZ Ph.D. Candidate, Research Assistant The Pennsylvania State University Electrical Engineering 329 Electrical Engineering East Building University Park, PA 16802 **CONFIDENTIAL** This e-mail message and any included attachments are confidential, intended only or the recipient named above, and may contain information that is privileged and exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient, please immediately notify the sender by return e-mail and delete all copies of this message. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] GNU Radio and USRP2 on the Gumstix and BeagleBoard
Hello: I am about to try to build and install GNU Radio 3.3.0 on a Gumstix Overo Water board. I have seen people on this list working with the BeagleBoard. I have some questions about this. 1. Both the Gumstix Overo Water and the BeagleBoard use a TI OMAP 3530, which uses an ARM Cortex A8 CPU. Since it contains a single-precision floating point unit, this should be adequate for running GNU Radio with floating point support, right? Here's more information on the ARM Cortex A8 CPU and the Gumstix: http://en.wikipedia.org/wiki/ARM_architecture http://www.arm.com/products/processors/cortex-a/cortex-a8.php http://www.gumstix.com/store/catalog/product_info.php?products_id=228 2. Should I use the GNU Radio 3.3.0 tarball from the website, or should I get the very latest code from git? Which git branch should I use? 3. I know the USRP2 requires a 1Gb Ethernet link, but the Gumstix and BeagleBoard only support 100 Mbps Ethernet. Is there any way around this? I am only going to use it for low-bandwidth signals, say around 100e6/500 = 200 kHz sample rates. Does anyone know whether 1 Gb Ethernet will be supported on the Gumstix or BeagleBoard anytime within the next six months? 4. The Gumstix Overo Water board uses OpenEmbedded Linux. Can GNU Radio work under this distribution, or must I use Ubuntu on my Gumstix? (I don't even know whether the Gumstix can run anything other than OpenEmbedded) Thanks a lot for your help!! Steve McMahon ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] spectrum_sense.py for usrp2
Hey! I am using USRP2 with XCVR2450 daughter board. when i execute the usrp2_rx_cfile.py it appends the data into a file but the size of file is way too big. in fraction of seconds it generates a file of 1 to 2GBs. I dont know whats going on in it. I am using the default decimation of 16. Secondly, I got the modified spectrum sense code for usrp2 from this forum i added fft mag_square part in it from usrp_spectrum_sense.py. whenever i run this code i get the error Failed to set center frequency. please help me out. I just want to collect the real time data for 2.4GHz ISM band. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNU Radio and USRP2 on the Gumstix and BeagleBoard
Hi Steve, On Nov 6, 2010, at 9:03 PM, Steve Mcmahon wrote: 4. The Gumstix Overo Water board uses OpenEmbedded Linux. Can GNU Radio work under this distribution, or must I use Ubuntu on my Gumstix? (I don't even know whether the Gumstix can run anything other than OpenEmbedded) OpenEmbedded is a convenient way to build the rootfs. When you build the omap3-console-image bitbake recipe, it builds the gcc cross compiler, begins with the prefix arm-angstrom-linux-gnueabi-* This compiler is usually located in your overo-oe/tmp/sysroots/x86_64-linux/usr/armv7a/bin folder If you specify the CROSS_COMPILE environment variable, it will automatically prefix the arm-angstrom-linux-gnueabi- part, so that instead of using the host gcc, it will use the arm-angstrom-linux-gnueabi-gcc version, thus allowing you to cross compile each package. e.g. make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi- I'm not certain if the whole GNU Radio stack will run on the Overo. You could try, and one way to start is to build a complete list of all required dependent packages, and check if recipes exist for them in overo-oe. You would need to build the missing ones, and then finally create a GNU Radio omap3-console-image that uses all of those packages, and build the rootfs. From my experience building GNU Radio from sources on Mac OS X, here is the list of dependent packages, and the order in which I built them. You can use this list to verify if OE recipe exist, and create new ones if it doesnt, to build your GNU Radio recipe. It shouldn't be too difficult, since most packages that compile on Ubuntu/Fedora linux should work just fine for the Overo, but I think it would take you at least 3 to 4 weeks to finish this task. GNU m4 autoconf automake GNU libiconv GNU libtool pkg-config asciidoc gettext getopt docbook-xsl docbook-xml xmlto GNU readline GNU MP multiple precision arithmetic library GNU Scientific Library guile libjpeg zlib libtiff libsdl FFTW library CppUnit SWIG boost C++ python uhd ? gnuradio I've skipped the list for wxwidgets, qt, some python libraries from this list. Best regards, Elvis Dowson ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] external reference clock REF CLOCK input on the USRP2
Hello: I have four USRP2 boards, each with a WBX board, and I have them setup to do the following for a ranging algorithm application: USRP2 #1: 901.001 MHz Tone Generator USRP2 #2: 901.002 MHz Tone Generator USRP2 #3: Capturing both tones and writing to file USRP2 #4: Capturing both tones and writing to file Each USRP2 board is connected to an antenna, so this is all over-the-air, not over Coaxial cable. When I capture the tones, or look at the output of USRP2 #1 and #2 on a spectrum analyzer, I notice they're not always exactly where I expect them to be, and this makes it hard to capture them and write the data to a file. I understand this because of the clock variability (clock drift) on the USRP2, and also because the four clocks are not synchronized together to a common source. Can I fix this and get absolute frequency precision by using the external reference clock REF CLOCK input on the USRP2? The REF CLOCK input takes a 10 MHz sine wave, 1 volt peak-to-peak, right? I have an HP signal generator, so could I use it to generate a 10 MHz sine and split its output four ways to each USRP2 board, right? Thanks for your help vetting out my ideas and my setup!! Steve McMahon ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0
Hello Thomas Spuhler: Yes, I would definitely be interested in your gcc 4.5 patch for Fedora. When you say patch, what do mean, it fixes gcc 4.5, or it fixes GNU Radio 3.3.0? Could you provide more explanation about this patch? I guess I'm not sure about what people are saying on this issue regarding my problem building GNU Radio 3.3.0 on openSUSE 11.3 using gcc 4.5. Is it gcc-4.5's fault (a bug in gcc), or gnuradio-3.3.0's fault (a bug in gnuradio)? One last question: Tom Rondeau mentioned that this issue will be fixed in GNU Radio 3.3.1. When is it expected to be released? Thanks again for your help, everyone. Steve McMahon --- On Fri, 11/5/10, Thomas Spuhler tho...@btspuhler.com wrote: From: Thomas Spuhler tho...@btspuhler.com Subject: Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0 To: discuss-gnuradio@gnu.org Date: Friday, November 5, 2010, 12:52 AM On Thursday, November 04, 2010 02:35:32 pm Tom Rondeau wrote: On Thu, Nov 4, 2010 at 5:06 PM, Eric Blossom e...@comsec.com wrote: On Thu, Nov 04, 2010 at 10:17:04AM -0700, Steve Mcmahon wrote: It took me a while to get some time to go back to my openSUSE 11.3 machine and regenerate the error message. Sorry, I should have done this when I made the initial post. So I successfully installed the following from source under openSUSE 11.3: Cheetah-2.4.2.1.tar.gz Markdown-2.0.3.tar.gz cppunit-1.12.1.tar.gz fftw-3.2.2.tar.gz gsl-1.14.tar.gz numpy-1.4.1.tar.gz sdcc-2.9.0-i386-unknown-linux2.5.tar.bz2 swig-1.3.40.tar.gz Then I do a ./configure for GNU Radio 3.3.0, and it runs fine, and it reports it's going to build everything that I need/that it should. However, when I do a make, it runs for a while, but then I get these errors: There's a much easier way to get where you're headed. Use the master branch in git. I'm pretty sure it has this problem fixed. http://www.gnuradio.org/redmine/wiki/gnuradio/Download Eric I just tried compiling from maint, master, and next on a new OpenSUSE 11.3 installation and all three compiled fine. It fails from the tarball for GNU Radio 3.3.0. So use one of the git versions for now. If you're on a machine not connected, just git clone gnuradio (master is probably the best branch to use) and tar it up to move it across to the other computer. That should work for you. When we get 3.3.1 out, this problem will be fixed. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio There is a patch for GCC4.5. I found it on Fedore. let me know if you ned it -- Thomas ___ 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] gcc 4.5 and GNU Radio 3.3.0
Hello: Thanks for your reply, Tom Rondeau. I guess I'm not sure about what people are saying on this issue regarding my problem building GNU Radio 3.3.0 on openSUSE 11.3 using gcc 4.5 -- is it gcc-4.5's fault (a bug in gcc), or gnuradio-3.3.0's fault (a bug in gnuradio)? I don't think I'm understanding the source of my problem correctly. Is my issue that gcc 4.5 cannot properly compile Boost 1.42, and that I need to use newer version of Boost with gcc-4.5, or is it that gnuradio-3.3.0 uses a C++ construct not supported in gcc-4.5, or is it a bug in gcc-4.5, or what? I am debating which work-around is easier for me: either install gcc-4.4.4 alongside gcc-4.5 on my openSUSE 11.3 machine and re-try gnuradio 3.3.0; or to download one of the Git versions (maint, master, or next) of gnuradio and re-try with gcc-4.5. Tom Rondeau mentioned that this issue will be fixed in GNU Radio 3.3.1. When is it expected to be released? Thanks a lot for your help everyone. Steve McMahon --- On Thu, 11/4/10, Tom Rondeau trondeau1...@gmail.com wrote: From: Tom Rondeau trondeau1...@gmail.com Subject: Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0 To: Eric Blossom e...@comsec.com, Steve Mcmahon steve.mcmaho...@yahoo.com, Tom Rondeau trondeau1...@gmail.com, discuss-gnuradio@gnu.org Date: Thursday, November 4, 2010, 9:35 PM On Thu, Nov 4, 2010 at 5:06 PM, Eric Blossom e...@comsec.com wrote: On Thu, Nov 04, 2010 at 10:17:04AM -0700, Steve Mcmahon wrote: It took me a while to get some time to go back to my openSUSE 11.3 machine and regenerate the error message. Sorry, I should have done this when I made the initial post. So I successfully installed the following from source under openSUSE 11.3: Cheetah-2.4.2.1.tar.gz Markdown-2.0.3.tar.gz cppunit-1.12.1.tar.gz fftw-3.2.2.tar.gz gsl-1.14.tar.gz numpy-1.4.1.tar.gz sdcc-2.9.0-i386-unknown-linux2.5.tar.bz2 swig-1.3.40.tar.gz Then I do a ./configure for GNU Radio 3.3.0, and it runs fine, and it reports it's going to build everything that I need/that it should. However, when I do a make, it runs for a while, but then I get these errors: There's a much easier way to get where you're headed. Use the master branch in git. I'm pretty sure it has this problem fixed. http://www.gnuradio.org/redmine/wiki/gnuradio/Download Eric I just tried compiling from maint, master, and next on a new OpenSUSE 11.3 installation and all three compiled fine. It fails from the tarball for GNU Radio 3.3.0. So use one of the git versions for now. If you're on a machine not connected, just git clone gnuradio (master is probably the best branch to use) and tar it up to move it across to the other computer. That should work for you. When we get 3.3.1 out, this problem will be fixed. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0
On Saturday, November 06, 2010 02:23:20 pm Steve Mcmahon wrote: Hello Thomas Spuhler: Yes, I would definitely be interested in your gcc 4.5 patch for Fedora. When you say patch, what do mean, it fixes gcc 4.5, or it fixes GNU Radio 3.3.0? Could you provide more explanation about this patch? I guess I'm not sure about what people are saying on this issue regarding my problem building GNU Radio 3.3.0 on openSUSE 11.3 using gcc 4.5. Is it gcc-4.5's fault (a bug in gcc), or gnuradio-3.3.0's fault (a bug in gnuradio)? One last question: Tom Rondeau mentioned that this issue will be fixed in GNU Radio 3.3.1. When is it expected to be released? Thanks again for your help, everyone. Steve McMahon --- On Fri, 11/5/10, Thomas Spuhler tho...@btspuhler.com wrote: From: Thomas Spuhler tho...@btspuhler.com Subject: Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0 To: discuss-gnuradio@gnu.org Date: Friday, November 5, 2010, 12:52 AM On Thursday, November 04, 2010 02:35:32 pm Tom Rondeau wrote: On Thu, Nov 4, 2010 at 5:06 PM, Eric Blossom e...@comsec.com wrote: On Thu, Nov 04, 2010 at 10:17:04AM -0700, Steve Mcmahon wrote: It took me a while to get some time to go back to my openSUSE 11.3 machine and regenerate the error message. Sorry, I should have done this when I made the initial post. So I successfully installed the following from source under openSUSE 11.3: Cheetah-2.4.2.1.tar.gz Markdown-2.0.3.tar.gz cppunit-1.12.1.tar.gz fftw-3.2.2.tar.gz gsl-1.14.tar.gz numpy-1.4.1.tar.gz sdcc-2.9.0-i386-unknown-linux2.5.tar.bz2 swig-1.3.40.tar.gz Then I do a ./configure for GNU Radio 3.3.0, and it runs fine, and it reports it's going to build everything that I need/that it should. However, when I do a make, it runs for a while, but then I get these errors: There's a much easier way to get where you're headed. Use the master branch in git. I'm pretty sure it has this problem fixed. http://www.gnuradio.org/redmine/wiki/gnuradio/Download Eric I just tried compiling from maint, master, and next on a new OpenSUSE 11.3 installation and all three compiled fine. It fails from the tarball for GNU Radio 3.3.0. So use one of the git versions for now. If you're on a machine not connected, just git clone gnuradio (master is probably the best branch to use) and tar it up to move it across to the other computer. That should work for you. When we get 3.3.1 out, this problem will be fixed. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio There is a patch for GCC4.5. I found it on Fedore. let me know if you ned it The patch makes it build with gcc4.5.1 but then it won't build with older gcc, You need to put an if statement into the spec file http://pastebin.mandriva.com/21172 and the patch: http://pastebin.mandriva.com/21173 -- Thomas ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gcc 4.5 and GNU Radio 3.3.0
On Sat, Nov 06, 2010 at 02:34:35PM -0700, Steve Mcmahon wrote:
Hello:
Thanks for your reply, Tom Rondeau.
I guess I'm not sure about what people are saying on this issue
regarding my problem building GNU Radio 3.3.0 on openSUSE 11.3 using
gcc 4.5 -- is it gcc-4.5's fault (a bug in gcc), or
gnuradio-3.3.0's fault (a bug in gnuradio)?
I don't think I'm understanding the source of my problem
correctly. Is my issue that gcc 4.5 cannot properly compile Boost
1.42, and that I need to use newer version of Boost with gcc-4.5, or
is it that gnuradio-3.3.0 uses a C++ construct not supported in
gcc-4.5, or is it a bug in gcc-4.5, or what?
I don't know about any boost/gcc problem. However we did fix a bug in
GNU Radio on 2010-08-04 in changeset d2888160c3fca8da2 that was for
gcc 4.5.0 compatibility.
The diff is attached.
Eric
diff --git a/usrp2/host/lib/usrp2.cc b/usrp2/host/lib/usrp2.cc
index f0ee564..0842482 100644
--- a/usrp2/host/lib/usrp2.cc
+++ b/usrp2/host/lib/usrp2.cc
@@ -38,9 +38,9 @@ namespace usrp2 {
struct usrp_table_entry {
// inteface + normalized mac addr (eth0:01:23:45:67:89:ab)
std::stringkey;
-boost::weak_ptrusrp2::usrp2 value;
+boost::weak_ptrusrp2 value;
-usrp_table_entry(const std::string _key, boost::weak_ptrusrp2::usrp2
_value)
+usrp_table_entry(const std::string _key, boost::weak_ptrusrp2 _value)
: key(_key), value(_value) {}
};
@@ -70,7 +70,7 @@ namespace usrp2 {
// We don't have the USRP2 we're looking for
// create a new one and stick it in the table.
-usrp2::sptr r(new usrp2::usrp2(ifc, pr, rx_bufsize));
+usrp2::sptr r(new usrp2(ifc, pr, rx_bufsize));
usrp_table_entry t(key, r);
s_table.push_back(t);
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
