QA OOT module test fails to find Gnuradio
Hello, I had the QA test working, but it produces an incorrect result. So I prepared the C++ OOT for debugging. To Configure the model for debugging, I picked a gcc debugger and in the json configuration file I copied over the info from another OOT json file into the current OOT and changed all the params to fit the current model. However, when I tried to compile, I get a "Set Gnuradio_Found False" error message. And, it gave the reason as: Gnuradio not found because dependency Boost could not be found. How do I fix this? Thanks for your help. George
Re: GNU radio logging
The config you shared has the messages going to stdout and stderr. Further many Gnu Radio blocks don’t even Produce any debugging output at runtime. Sent from my iPhone > On Sep 14, 2020, at 6:45 PM, Xiang Ma wrote: > > > There is no output in the configured log file. > >> On Mon, Sep 14, 2020 at 4:43 PM Marcus D Leech >> wrote: >> Please define “does not work”. >> >> >> >> Sent from my iPhone >> On Sep 14, 2020, at 6:35 PM, Xiang Ma wrote: >>> >>> Hi, >>> >>> I want to print the logging information of the gnuradio. I checked the >>> website https://wiki.gnuradio.org/index.php/Logging, it is kind of >>> outdated. >>> >>> hu@hu:~/Documents/marxwolf.github.io$ gnuradio-config-info --version >>> 3.7.14.0 >>> This is the gnuradio version on my Ubuntu 18.04. TO make the logging >>> configuration work in system level, I try to edit vim >>> /usr/local/etc/gnuradio/conf.d/gnuradio-runtime.conf file, >>> >>> [LOG] >>> # Levels can be (case insensitive): >>> # DEBUG, INFO, WARN, TRACE, ERROR, ALERT, CRIT, FATAL, EMERG >>> log_level = debug >>> debug_level = emerg >>> >>> # These file names can either be 'stdout' to output to standard output >>> # or 'stderr' to output to standard error. Any other string will >>> # create a file in which to output the logging information. An empty >>> # string or no value here will ignore this level of configuration >>> # completely. >>> log_file = stdout >>> debug_file = stderr >>> >>> # Used for advanced configuration of the logger >>> #log_config = /usr/local/etc/gnuradio/gr_log_default.xml >>> >>> I edit the log_level and log_file, but it does not work. And I am not sure >>> why. Please help me. >>> Best Regards, >>> >>> Xiang Ma >>> >>> -- >>> Xiang Ma, Ph.D. Student >>> College of Engineering >>> Utah State University >>> E-mail:marxwo...@gmail.com > > > -- > Xiang Ma, Ph.D. Student > College of Engineering > Utah State University > E-mail:marxwo...@gmail.com
Re: GNU radio logging
There is no output in the configured log file. On Mon, Sep 14, 2020 at 4:43 PM Marcus D Leech wrote: > Please define “does not work”. > > > > Sent from my iPhone > > On Sep 14, 2020, at 6:35 PM, Xiang Ma wrote: > > > Hi, > > I want to print the logging information of the gnuradio. I checked the > website https://wiki.gnuradio.org/index.php/Logging, it is kind of > outdated. > > hu@hu:~/Documents/marxwolf.github.io$ gnuradio-config-info --version > 3.7.14.0 > This is the gnuradio version on my Ubuntu 18.04. TO make the logging > configuration work in system level, I try to edit vim > /usr/local/etc/gnuradio/conf.d/gnuradio-runtime.conf file, > > [LOG] > # Levels can be (case insensitive): > # DEBUG, INFO, WARN, TRACE, ERROR, ALERT, CRIT, FATAL, EMERG > log_level = debug > debug_level = emerg > > # These file names can either be 'stdout' to output to standard output > # or 'stderr' to output to standard error. Any other string will > # create a file in which to output the logging information. An empty > # string or no value here will ignore this level of configuration > # completely. > log_file = stdout > debug_file = stderr > > # Used for advanced configuration of the logger > #log_config = /usr/local/etc/gnuradio/gr_log_default.xml > > I edit the log_level and log_file, but it does not work. And I am not sure > why. Please help me. > Best Regards, > > Xiang Ma > > -- > *Xiang Ma, *Ph.D. Student > College of Engineering > Utah State University > E-mail:marxwo...@gmail.com > > -- *Xiang Ma, *Ph.D. Student College of Engineering Utah State University E-mail:marxwo...@gmail.com
Re: GNU radio logging
Please define “does not work”. Sent from my iPhone > On Sep 14, 2020, at 6:35 PM, Xiang Ma wrote: > > > Hi, > > I want to print the logging information of the gnuradio. I checked the > website https://wiki.gnuradio.org/index.php/Logging, it is kind of outdated. > > hu@hu:~/Documents/marxwolf.github.io$ gnuradio-config-info --version > 3.7.14.0 > This is the gnuradio version on my Ubuntu 18.04. TO make the logging > configuration work in system level, I try to edit vim > /usr/local/etc/gnuradio/conf.d/gnuradio-runtime.conf file, > > [LOG] > # Levels can be (case insensitive): > # DEBUG, INFO, WARN, TRACE, ERROR, ALERT, CRIT, FATAL, EMERG > log_level = debug > debug_level = emerg > > # These file names can either be 'stdout' to output to standard output > # or 'stderr' to output to standard error. Any other string will > # create a file in which to output the logging information. An empty > # string or no value here will ignore this level of configuration > # completely. > log_file = stdout > debug_file = stderr > > # Used for advanced configuration of the logger > #log_config = /usr/local/etc/gnuradio/gr_log_default.xml > > I edit the log_level and log_file, but it does not work. And I am not sure > why. Please help me. > Best Regards, > > Xiang Ma > > -- > Xiang Ma, Ph.D. Student > College of Engineering > Utah State University > E-mail:marxwo...@gmail.com
gr-osmosdr link error with target_link_libraries
Hello All, Just a quick patch for gr-blocks/lib/CMakeLists.txt. I find without this patch the command passes sndfile::sndfile to the linker, which causes a gr-osmosdr build to fail. I am using a LFS-10.0 install and have libsndfile installed. I'm not sure this patch is necessary, but it fixes the error on my system. Please let me know if this should be fixed elsewhere, or if it causes any breakages. Chris From 0385eadbe2e7ebcf3d0e6820c39e03f118763f10 Mon Sep 17 00:00:00 2001 From: Chris Gorman Date: Mon, 14 Sep 2020 18:19:24 -0400 Subject: [PATCH] target_link_libraries sndfile::sndfile causes link error in gr-osmosdr use of sndfile::sndfile causes linker error when trying to build gr-osmosdr. Change to sndfile links properly. --- gr-blocks/lib/CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gr-blocks/lib/CMakeLists.txt b/gr-blocks/lib/CMakeLists.txt index c867d0ab0..c4ccf60d7 100644 --- a/gr-blocks/lib/CMakeLists.txt +++ b/gr-blocks/lib/CMakeLists.txt @@ -175,7 +175,7 @@ add_library(gnuradio-blocks target_link_libraries(gnuradio-blocks gnuradio-runtime Volk::volk -sndfile::sndfile +sndfile ) target_include_directories(gnuradio-blocks -- 2.28.0
GNU radio logging
Hi, I want to print the logging information of the gnuradio. I checked the website https://wiki.gnuradio.org/index.php/Logging, it is kind of outdated. hu@hu:~/Documents/marxwolf.github.io$ gnuradio-config-info --version 3.7.14.0 This is the gnuradio version on my Ubuntu 18.04. TO make the logging configuration work in system level, I try to edit vim /usr/local/etc/gnuradio/conf.d/gnuradio-runtime.conf file, [LOG] # Levels can be (case insensitive): # DEBUG, INFO, WARN, TRACE, ERROR, ALERT, CRIT, FATAL, EMERG log_level = debug debug_level = emerg # These file names can either be 'stdout' to output to standard output # or 'stderr' to output to standard error. Any other string will # create a file in which to output the logging information. An empty # string or no value here will ignore this level of configuration # completely. log_file = stdout debug_file = stderr # Used for advanced configuration of the logger #log_config = /usr/local/etc/gnuradio/gr_log_default.xml I edit the log_level and log_file, but it does not work. And I am not sure why. Please help me. Best Regards, Xiang Ma -- *Xiang Ma, *Ph.D. Student College of Engineering Utah State University E-mail:marxwo...@gmail.com
Re: Porting gr-osmosdr to gr-3.9 without swig.
Hi Chris, I started gr-osmosdr some month ago, but I had to interrupt due to other coding needs. What gr-osmosdr repository did you start with ? I forked https://github.com/argilo/gr-osmosdr.git which had some preparations for 3.9, but at that time gr3.9 still used swig. First I ported successfully some of my oot modules to 3.9 the way described in the porting guide. But for more complex modules I tried another way. I removed the swig part and looked at my ported modules, how to add the pybind part. At the moment I'm at the point af generating the bindings. -- Volker
