Re: Difficulty in compiling gnuradio from git on opensuse 15.3

2022-01-18 Thread li...@lazygranch.com
:41 -0800 Ron Economos wrote: > You probably also need -DCMAKE_CXX_COMPILER=g++-11 on your CMake > command line. > > Ron > > On 1/18/22 4:39 PM, li...@lazygranch.com wrote: > > I looked at > > https://build.opensuse.org/package/show/home:wkazubski:test:science/gnur

Re: Difficulty in compiling gnuradio from git on opensuse 15.3

2022-01-18 Thread li...@lazygranch.com
I looked at https://build.opensuse.org/package/show/home:wkazubski:test:science/gnuradio39 I clicked around a bit but I don't know specifically where you get the package list. The only one I can't load is for plotting. I have it but Cmake doesn't find it. "Python checking for pyqtgraph - not

Re: Difficulty in compiling gnuradio from git on opensuse 15.3

2022-01-18 Thread li...@lazygranch.com
I have that file. On Tue, 18 Jan 2022 05:51:45 -0500 Jeff Long wrote: > Check to see whether the boost filesystem package is installed. Not > familiar with packaging for that distro - looks like it would be > "libboost_filesystem1_75_0-devel". > > On Tue, J

Difficulty in compiling gnuradio from git on opensuse 15.3

2022-01-18 Thread li...@lazygranch.com
I just upgraded my Opensuse from 15.2 to rev 15.3. I compiled gnuradio 3.9 maintenance release using the instructions from https://wiki.gnuradio.org/index.php/InstallingGR#From_Source Results: -- building release 3.9.0.0 100% tests passed, 0 tests failed out of 252 Total Test time

Re: gnuradio compilation and also gr-air-modes issue

2021-11-08 Thread li...@lazygranch.com
our install of GNU radio 3.9. > > There is a branch on gr-air-modes called "gr3.9" that looks like it > could work, although the commit messages say "WIP with plenty of > untested code". To switch to that branch: > > git checkout gr3.9 > >

gnuradio compilation and also gr-air-modes issue

2021-11-07 Thread li...@lazygranch.com
Yes I know this list is specifically for gnuradio. I just compiled 3.9.0.4 from source (github) on opensuse 15.2 and all went well. When I ran the "make test" it seemed a bit slow then I realized I forgot to specify the number of CPUs (the j option). Doing a "make clean" then the properly flaged

Re: "modules" GMP and MPIR;3.9.0.0

2021-01-27 Thread li...@lazygranch.com
This sure is crypic. So missing MPIR but finding MPLIB is the same thing? Dependency MPLIB_FOUND = TRUE And this means I actually did find THIRFT? Could NOT find THRIFT (missing: PYTHON_THRIFT_FOUND THRIFT_FOUND) Do these "cancel"? -- Python checking for pygccxml - not found -- Found

"modules" GMP and MPIR;3.9.0.0

2021-01-27 Thread li...@lazygranch.com
Building 3.9.0.0 on opensuse 15.2. I did git checkout maint-3.9 I'm using volk from the repo. (not building it) The terminology "module" confuses me. Does this refer to gnuradio code or some library on my computer? I believe I have gmp and mpir available. -- Checking for module 'gmp' -- No

Re: [Discuss-gnuradio] An analog RF question

2018-05-20 Thread li...@lazygranch.com
pnet.com> wrote: > On 05/20/2018 09:13 PM, li...@lazygranch.com wrote: > > > > Can you be more specific about the corner frequency? > Corner frequencies step-tunable from perhaps 20Mhz down to perhaps > 2MHz. > > Many chips, like the R820T2, the MAX2112, and the

Re: [Discuss-gnuradio] An analog RF question

2018-05-20 Thread li...@lazygranch.com
On Sun, 20 May 2018 20:54:34 -0400 "Marcus D. Leech" wrote: > Does anyone here know how various high-integration tuners achieve > more-or-less continuously-variable corner low-pass frequency on the > baseband outputs? > > I'm aware of switched-capacitor filters, but my

Re: [Discuss-gnuradio] gnuradio radio test repeatability

2017-06-08 Thread li...@lazygranch.com
er_bf > 13/14 Test #13: qa_ber_bf Passed1.12 > sec Start 14: qa_fecapi_cc > 14/14 Test #14: qa_fecapi_cc . Passed3.05 > sec > > 100% tests passed, 0 tests failed out of 14 > > Total Test time (real) = 47.42 sec > &

Re: [Discuss-gnuradio] gnuradio radio test repeatability

2017-06-08 Thread li...@lazygranch.com
As a follow up, the memtest found no errors. On Thu, 8 Jun 2017 01:47:43 -0700 "li...@lazygranch.com" <li...@lazygranch.com> wrote: > I downloaded gnuradio off of github. Hopefully this is sufficient > identification of the version: > > "Latest commit 37d373a

[Discuss-gnuradio] gnuradio radio test repeatability

2017-06-08 Thread li...@lazygranch.com
I downloaded gnuradio off of github. Hopefully this is sufficient identification of the version: "Latest commit 37d373a 14 hours ago @jmcorgan jmcorgan Merge branch 'maint'" I noticed ZMQ failed, which is odd since it worked before. I reran the test and ZMQ worked. This makes me wonder if some

Re: [Discuss-gnuradio] GSL Gnu Scientific Library 2.3

2017-05-24 Thread li...@lazygranch.com
Wed, 24 May 2017 10:22:36 +0200 Marcus Müller <marcus.muel...@ettus.com> wrote: > Still using an older GSL myself, but what does `ctest -VV -R polar` in > the build directory give you in detailed problems? > > Best regards, > > Marcus > > > On

Re: [Discuss-gnuradio] Building gnuradio master fails

2017-05-23 Thread li...@lazygranch.com
son <cinaed.sim...@gmail.com> wrote: > On 05/21/2017 08:02 PM, li...@lazygranch.com wrote: > > It seems opensuse runs an old rev of gsl. Here are the relevant file > > names and revs: > > > > gsl 1.16-74 > > gsl-devel 2.3-9.1 > > libgsl19 2.3-9.1 > > libg

Re: [Discuss-gnuradio] Building gnuradio master fails

2017-05-21 Thread li...@lazygranch.com
of programs such as krita and more significant, inkscape. I can build what breaks from source if the rev of gsl is the problem. On Sun, 21 May 2017 18:08:36 -0700 li...@lazygranch.com wrote: > > "Latest commit 0e32fca 4 days ago." That comes right off of github. > https://

Re: [Discuss-gnuradio] Building gnuradio master fails

2017-05-21 Thread li...@lazygranch.com
Ralph A. Schmid, dk5ras" <ra...@schmid.xxx> wrote: > This is also my experience, I made exactly this, deleting the build > dir, make a new one, fresh cmake, and so on. > > Ralph. > > > > -----Original Message- > > From: li...@lazygranch.com [mailto:li

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

2017-04-30 Thread li...@lazygranch.com
ash > associated with the commit. For example: > > git checkout 082711c > > will go back two commits, and you'll be building > 3.7.12git-99-g082711cc. > > Then you can always get back to where you started by typing: > > git checkout master > > Ron > > On 04/

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

2017-04-30 Thread li...@lazygranch.com
On opensuse it is python-scipy. Those tests did work at one time, and I do recall having to load python-scipy. zmq is the one I find confusing. You can find references to 0mq, zmq, and zeromq in documentation. For packages, they stuck wit zmq: czmq czmq-devel libczmq3 libzmq5 python-pyzmq

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

2017-04-29 Thread li...@lazygranch.com
s-gnuradio] test and build errors on > > 3.7.12git-101-g098dc3e0 > > > > On 04/29/2017 05:52 PM, li...@lazygranch.com wrote: > >> I have ZMQ. Here is the cmake finding it: > >> > >> -- Configuring gr-wxgui support... > >> -- Depen

Re: [Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

2017-04-29 Thread li...@lazygranch.com
py > > python-zmq > > Ron > > On 04/29/2017 11:31 AM, li...@lazygranch.com wrote: > > Opensuse 42.2 > > uname -a > > Linux linux-0u81 4.4.57-18.3-default #1 SMP Thu Mar 30 06:39:47 UTC > > 2017 (39c8557) x86_64 x86_64 x86_64 GNU/Linux > > ---

[Discuss-gnuradio] test and build errors on 3.7.12git-101-g098dc3e0

2017-04-29 Thread li...@lazygranch.com
Opensuse 42.2 uname -a Linux linux-0u81 4.4.57-18.3-default #1 SMP Thu Mar 30 06:39:47 UTC 2017 (39c8557) x86_64 x86_64 x86_64 GNU/Linux --- Building for version: 3.7.12git-101-g098dc3e0 / 3.7.12git Entire cmake output at: https://pastebin.com/Gqa32538 -- Errors in the doxygen

Re: [Discuss-gnuradio] CMake error related to log4cpp in non-standard location

2017-04-29 Thread li...@lazygranch.com
On the other hand, the current git pull has fixed the LOG4CPP problem I had with opensuse 42.2. http://gnuradio.4.n7.nabble.com/fail-tests-for-qa-cpp-py-binding-qa-cpp-py-binding-set-qa-ctrlport-probes-td63291.html It now works for both the local library build of log4cpp and the standard

Re: [Discuss-gnuradio] log4cpp library not found

2017-04-03 Thread li...@lazygranch.com
l.com> wrote: > On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: > > Regarding the Marcus cmake, I guessed that src would copy to lib, > > but that didn't happen. (Easy to check by file dates.) I ended up > > copying the new FindLog4cpp.cmake to both locations myself.

Re: [Discuss-gnuradio] log4cpp library not found

2017-04-02 Thread li...@lazygranch.com
the "normal" library (/usr/lib64) rather than the local library, but that didn't work either. So in summary, the problem is still there. On Sun, 2 Apr 2017 14:16:07 -0700 Cinaed Simson <cinaed.sim...@gmail.com> wrote: > On 04/01/2017 03:40 PM, li...@lazygranch.com wrote: &g

Re: [Discuss-gnuradio] log4cpp library not found

2017-04-01 Thread li...@lazygranch.com
on with that > cmake/Modules/FindLog4cpp.cmake, probably. > > Can you replace that Find...cmake with the one I've attached and give > it a try? > > Cheers, > > Marcus > > > On 01.04.2017 18:27, li...@lazygranch.com wrote: > > Hyphen instead of underscore. > > >

Re: [Discuss-gnuradio] log4cpp library not found

2017-04-01 Thread li...@lazygranch.com
Try running > > pkg_config --libs log4cpp > > If that fails: Please make sure the installation put the packageconfig > files in a place that packageconfig looks into. > > Best regards, > Marcus > > On 04/01/2017 11:13 AM, li...@lazygranch.com wrote: > > I bui

Re: [Discuss-gnuradio] log4cpp library not found

2017-04-01 Thread li...@lazygranch.com
the SF build. On Fri, 31 Mar 2017 22:07:59 -0400 "Marcus D. Leech" <mle...@ripnet.com> wrote: > On 03/31/2017 09:13 PM, li...@lazygranch.com wrote: > > opensuse 42.2 > > > > This is the only "missing" thing I can find in the cmake

[Discuss-gnuradio] log4cpp library not found

2017-03-31 Thread li...@lazygranch.com
opensuse 42.2 This is the only "missing" thing I can find in the cmake ..: -- Configuring volk support... -- Enabling volk support. -- Override with -DENABLE_VOLK=ON/OFF -- Override with -DENABLE_INTERNAL_VOLK=ON/OFF -- ENABLE_GR_LOG set to ON. -- HAVE_LOG4CPP set to False. --

Re: [Discuss-gnuradio] fail tests for qa_cpp_py_binding qa_cpp_py_binding_set qa_ctrlport_probes

2017-03-27 Thread li...@lazygranch.com
> >> > >> could you share the output of > >> > >> ctest -V -R cpp_py > >> > >> ctest -V -R ctrlport_probes > >> > >> with us? > >> > >> > >> Regarding Boost: well, yeah, 1.54. is indeed not very rece

Re: [Discuss-gnuradio] fail tests for qa_cpp_py_binding qa_cpp_py_binding_set qa_ctrlport_probes

2017-03-26 Thread li...@lazygranch.com
Same goes for the slightly dusty GCC 4.8.5; however, > it's pretty uncommon to see a rather recent SWIG (3.0.10 in your > case) paired with these two. So that's a bit surprising! > > Best regards, > Marcus > > On 03/26/2017 12:16 PM, li...@lazygranch.com wrote: > > From m

[Discuss-gnuradio] fail tests for qa_cpp_py_binding qa_cpp_py_binding_set qa_ctrlport_probes

2017-03-26 Thread li...@lazygranch.com
>From make test: The following tests FAILED: 24 - qa_cpp_py_binding (Failed) 25 - qa_cpp_py_binding_set (Failed) 26 - qa_ctrlport_probes (Failed) Building for version: 3.7.12git-44-g0d5fd62c / 3.7.12git Linux linux.suse 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC