date:20210527

Re: launching gnuradio generated python file core dumps

2021-05-27 Thread Jeff Long

Looks like a double-free in the destructor for the number sink. Please add
an issue. Shouldn't slow you down though since it only happens on exit.

On Thu, May 27, 2021 at 8:04 PM Chris Gorman 
wrote:

> Hello All,
>
> I'm generating a python file that attempts to replicate Victor Cai's
> MFCW radar.  I don't know for sure if I've implemented it correctly,
> but it causes a core dump when run.  I'm using the feature/gr-iio
> branch, v3.10.0.0git-341-g131f32c7.  I don't have to run the program,
> just launch and close the window and I get the following...
>
> [chris@descartes radar]$ ./mfcw.py
> free(): invalid pointer
> Aborted (core dumped)
>
> When I run the program using gdb, I get...
>
> (gdb) run mfcw.py
> Starting program: /usr/bin/python mfcw.py
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> [New Thread 0x7fffe6b80640 (LWP 50441)]
> [New Thread 0x7fffe635d640 (LWP 50442)]
> [New Thread 0x7fffe5910640 (LWP 50443)]
> [Thread 0x7fffe5910640 (LWP 50443) exited]
> [New Thread 0x7fffe5910640 (LWP 50444)]
> [New Thread 0x7fffe510f640 (LWP 50445)]
> ---snip---
> [New Thread 0x7fff75d9f640 (LWP 50473)]
> [New Thread 0x7fff7559e640 (LWP 50476)]
> [Thread 0x7fff927fc640 (LWP 50464) exited]
> [Thread 0x7fff92ffd640 (LWP 50463) exited]
> ---snip---
> [Thread 0x7fffd7e67640 (LWP 50447) exited]
> [Thread 0x7fffb3fff640 (LWP 50454) exited]
> [Thread 0x7fff7559e640 (LWP 50476) exited]
> [Thread 0x7fff765a0640 (LWP 50472) exited]
> [Thread 0x7fff75d9f640 (LWP 50473) exited]
> [Thread 0x7fff80ff9640 (LWP 50471) exited]
> [Thread 0x7fff817fa640 (LWP 50470) exited]
> [Thread 0x7fffe6b80640 (LWP 50441) exited]
> [Thread 0x7fff81ffb640 (LWP 50469) exited]
> [Thread 0x7fff827fc640 (LWP 50468) exited]
> [Thread 0x7fff82ffd640 (LWP 50467) exited]
> [Thread 0x7fff837fe640 (LWP 50466) exited]
> [Thread 0x7fff83fff640 (LWP 50465) exited]
> free(): invalid pointer
> Thread 1 "python" received signal SIGABRT, Aborted.
> 0x77a58d22 in raise () from /usr/lib/libc.so.6
> (gdb) bt
> #0  0x77a58d22 in raise () at /usr/lib/libc.so.6
> #1  0x77a42862 in abort () at /usr/lib/libc.so.6
> #2  0x77a9ad28 in __libc_message () at /usr/lib/libc.so.6
> #3  0x77aa292a in  () at /usr/lib/libc.so.6
> #4  0x77aa3cfc in _int_free () at /usr/lib/libc.so.6
> #5  0x77aa79e8 in free () at /usr/lib/libc.so.6
> #6  0x7fffeb1dfd6f in gr::qtgui::number_sink_impl::~number_sink_impl()
> ()
> at /usr/local/lib/libgnuradio-qtgui.so.3.10.0git
> #7  0x7fffeb1e0123 in virtual thunk to
> gr::qtgui::number_sink_impl::~number_sink_impl() () at
> /usr/local/lib/libgnuradio-qtgui.so.3.10.0git
> #8  0x7fffeb356e0a in  ()
> at /usr/local/lib/python3.9/site-packages/gnuradio/qtgui/
> qtgui_python.cpython-39-x86_64-linux-gnu.so
> #9  0x7fffeb37bce6 in  ()
> at /usr/local/lib/python3.9/site-packages/gnuradio/qtgui/
> qtgui_python.cpython-39-x86_64-linux-gnu.so
> #10 0x7fffeb34f9c4 in  ()
> at /usr/local/lib/python3.9/site-packages/gnuradio/qtgui/
> qtgui_python.cpython-39-x86_64-linux-gnu.so
> #11 0x77d09cb6 in  () at /usr/lib/libpython3.9.so.1.0
> #12 0x76d98f26 in  ()
> at /usr/lib/python3.9/site-packages/PyQt5/
> sip.cpython-39-x86_64-linux-gnu.so
> #13 0x76d9a194 in  ()
> at /usr/lib/python3.9/site-packages/PyQt5/
> sip.cpython-39-x86_64-linux-gnu.so
> #14 0x77d029ac in  () at /usr/lib/libpython3.9.so.1.0
> #15 0x77dc17de in  () at /usr/lib/libpython3.9.so.1.0
> #16 0x77df09ba in PyGC_Collect () at /usr/lib/libpython3.9.so.1.0
> #17 0x77dee8a9 in Py_FinalizeEx () at /usr/lib/libpython3.9.so.1.0
> #18 0x77de643c in Py_RunMain () at /usr/lib/libpython3.9.so.1.0
> #19 0x77db7349 in Py_BytesMain () at /usr/lib/libpython3.9.so.1.0
> #20 0x77a43b25 in __libc_start_main () at /usr/lib/libc.so.6
> #21 0x504e in _start ()
>
> Since my last post was a known bug, I searched the issue tracker at
> github for gnuradio, but I couldn't find anything about this one.
> Should I move this there?
>
> Thanks in advance,
>
> Chris
>

launching gnuradio generated python file core dumps

2021-05-27 Thread Chris Gorman

Hello All,

I'm generating a python file that attempts to replicate Victor Cai's
MFCW radar.  I don't know for sure if I've implemented it correctly,
but it causes a core dump when run.  I'm using the feature/gr-iio
branch, v3.10.0.0git-341-g131f32c7.  I don't have to run the program,
just launch and close the window and I get the following...

[chris@descartes radar]$ ./mfcw.py
free(): invalid pointer
Aborted (core dumped)

When I run the program using gdb, I get...

(gdb) run mfcw.py
Starting program: /usr/bin/python mfcw.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe6b80640 (LWP 50441)]
[New Thread 0x7fffe635d640 (LWP 50442)]
[New Thread 0x7fffe5910640 (LWP 50443)]
[Thread 0x7fffe5910640 (LWP 50443) exited]
[New Thread 0x7fffe5910640 (LWP 50444)]
[New Thread 0x7fffe510f640 (LWP 50445)]
---snip---
[New Thread 0x7fff75d9f640 (LWP 50473)]
[New Thread 0x7fff7559e640 (LWP 50476)]
[Thread 0x7fff927fc640 (LWP 50464) exited]
[Thread 0x7fff92ffd640 (LWP 50463) exited]
---snip---
[Thread 0x7fffd7e67640 (LWP 50447) exited]
[Thread 0x7fffb3fff640 (LWP 50454) exited]
[Thread 0x7fff7559e640 (LWP 50476) exited]
[Thread 0x7fff765a0640 (LWP 50472) exited]
[Thread 0x7fff75d9f640 (LWP 50473) exited]
[Thread 0x7fff80ff9640 (LWP 50471) exited]
[Thread 0x7fff817fa640 (LWP 50470) exited]
[Thread 0x7fffe6b80640 (LWP 50441) exited]
[Thread 0x7fff81ffb640 (LWP 50469) exited]
[Thread 0x7fff827fc640 (LWP 50468) exited]
[Thread 0x7fff82ffd640 (LWP 50467) exited]
[Thread 0x7fff837fe640 (LWP 50466) exited]
[Thread 0x7fff83fff640 (LWP 50465) exited]
free(): invalid pointer
Thread 1 "python" received signal SIGABRT, Aborted.
0x77a58d22 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x77a58d22 in raise () at /usr/lib/libc.so.6
#1  0x77a42862 in abort () at /usr/lib/libc.so.6
#2  0x77a9ad28 in __libc_message () at /usr/lib/libc.so.6
#3  0x77aa292a in  () at /usr/lib/libc.so.6
#4  0x77aa3cfc in _int_free () at /usr/lib/libc.so.6
#5  0x77aa79e8 in free () at /usr/lib/libc.so.6
#6  0x7fffeb1dfd6f in gr::qtgui::number_sink_impl::~number_sink_impl() ()
at /usr/local/lib/libgnuradio-qtgui.so.3.10.0git
#7  0x7fffeb1e0123 in virtual thunk to
gr::qtgui::number_sink_impl::~number_sink_impl() () at
/usr/local/lib/libgnuradio-qtgui.so.3.10.0git
#8  0x7fffeb356e0a in  ()
at 
/usr/local/lib/python3.9/site-packages/gnuradio/qtgui/qtgui_python.cpython-39-x86_64-linux-gnu.so
#9  0x7fffeb37bce6 in  ()
at 
/usr/local/lib/python3.9/site-packages/gnuradio/qtgui/qtgui_python.cpython-39-x86_64-linux-gnu.so
#10 0x7fffeb34f9c4 in  ()
at 
/usr/local/lib/python3.9/site-packages/gnuradio/qtgui/qtgui_python.cpython-39-x86_64-linux-gnu.so
#11 0x77d09cb6 in  () at /usr/lib/libpython3.9.so.1.0
#12 0x76d98f26 in  ()
at /usr/lib/python3.9/site-packages/PyQt5/sip.cpython-39-x86_64-linux-gnu.so
#13 0x76d9a194 in  ()
at /usr/lib/python3.9/site-packages/PyQt5/sip.cpython-39-x86_64-linux-gnu.so
#14 0x77d029ac in  () at /usr/lib/libpython3.9.so.1.0
#15 0x77dc17de in  () at /usr/lib/libpython3.9.so.1.0
#16 0x77df09ba in PyGC_Collect () at /usr/lib/libpython3.9.so.1.0
#17 0x77dee8a9 in Py_FinalizeEx () at /usr/lib/libpython3.9.so.1.0
#18 0x77de643c in Py_RunMain () at /usr/lib/libpython3.9.so.1.0
#19 0x77db7349 in Py_BytesMain () at /usr/lib/libpython3.9.so.1.0
#20 0x77a43b25 in __libc_start_main () at /usr/lib/libc.so.6
#21 0x504e in _start ()

Since my last post was a known bug, I searched the issue tracker at
github for gnuradio, but I couldn't find anything about this one.
Should I move this there?

Thanks in advance,

Chris


mfcw.grc
Description: application/gnuradio-grc

Recommendation for PCI-based SDR frontends

2021-05-27 Thread Moses Browne Mwakyanjala

Hi everyone,
I'm looking for stable and affordable SDRs that can be connected and
slotted into the computer through the standard  PCI bus. So far I have only
found XTRX. I was wondering if there were other tested solutions out there.

Regards,

Moses.

Re: Problem changing LO with qt-gui range on Pluto SDR

2021-05-27 Thread David Winter

Hi Chris,

apparently you just discovered a bug, that just by chance, has already
been fixed. Simply update to the latest feature/gr-iio and you'll be
good to go.

If you're interested in what went wrong, the set_params call erroneously
included the buffer_size, see [0] vs [1].

David

[0]
https://github.com/gnuradio/gnuradio/blob/da099c070c2d61607e40dbcaedeb0474e974c9a2/gr-iio/grc/iio_pluto_source.block.yml#L114
[1]
https://github.com/gnuradio/gnuradio/blob/da099c070c2d61607e40dbcaedeb0474e974c9a2/gr-iio/python/iio/bindings/pluto_source_python.cc#L58-L72

On 5/27/21 10:10 PM, Chris Gorman wrote:
> Invoked with:  0x7f7c4a0095b0>, 10240, 1536000, 2000, 32768, True, True,
> True, 'slow_attack', 64, 'Design', '', 384000.0, 512000.0

Problem changing LO with qt-gui range on Pluto SDR

2021-05-27 Thread Chris Gorman

Hello All,

I am having difficulty using a qt-gui range with my plutosdr to change
the LO frequency.  I am using the feature/gr-iio branch,
v3.10.0.0git-297-gb13303bd.  When I run my python file and try to
change the LO frequency with a qt-gui range, I get the following
error.

[chris@descartes gnuradio]$ ./pluto_radio.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/gnuradio/qtgui/range.py",
line 186, in changed
self.notifyChanged(self.rangeType(val))
  File "/usr/local/lib/python3.9/site-packages/gnuradio/qtgui/range.py",
line 285, in sliderChanged
self.notifyChanged(self.rangeType(value))
  File "/home/chris/src/gnuradio/./pluto_radio.py", line 233, in set_f
   self.iio_pluto_source_0.set_params(int(self.f*1e6), self.samp_rate,
2000, 32768, True, True, True, 'slow_attack', 64, 'Design', '',
self.samp_rate/4, self.samp_rate/3)
TypeError: set_params(): incompatible function arguments. The
following argument types are supported:
1. (self: gnuradio.iio.iio_python.pluto_source, longfrequency:
int, samplerate: int, bandwidth: int, quadrature: bool, rfdc: bool,
bbdc: bool, gain: str, gain_value: float, filter_source: str = '',
filter_filename: str = '', Fpass: float = 0.0, Fstop: float = 0.0) ->
None

Invoked with: , 10240, 1536000, 2000, 32768, True, True,
True, 'slow_attack', 64, 'Design', '', 384000.0, 512000.0
Aborted (core dumped)

The python file is generated from the attached pluto_radio.grc file.

Should I create a ticket for this?

Thanks in advance,

Chris


pluto_radio.grc
Description: application/gnuradio-grc

Re: libosmo-dsp build hangs (required for gr-osmosdr)

2021-05-27 Thread Jeff Long

I'd commented out fcd in the deps for gr-osmosdr. Here's what I currently
have for diffs to gr-recipes:

$ git diff | cat
diff --git a/gr-osmosdr.lwr b/gr-osmosdr.lwr
index f40f1f9..5d2b084 100644
--- a/gr-osmosdr.lwr
+++ b/gr-osmosdr.lwr
@@ -29,11 +29,12 @@ depends:
 - airspy
 - airspyhf
 - soapysdr
-- gr-fcdproplus
+#- gr-fcdproplus
 description: Interface API independent of the underlying radio hardware
 gitbranch: master
 inherit: cmake
 # Let's always build this from source, not binaries
 source: git+https://git.osmocom.org/gr-osmosdr
+mirror: git+https://github.com/osmocom/gr-osmosdr
 vars:
   config_opt: ' -DENABLE_NONFREE=TRUE '
diff --git a/libhidapi.lwr b/libhidapi.lwr
index b0c817b..23c7e89 100644
--- a/libhidapi.lwr
+++ b/libhidapi.lwr
@@ -23,5 +23,6 @@ depends:
 inherit: autoconf
 satisfy:
   deb: libhidapi-dev
+  rpm: hidapi-devel
   pacman: hidapi
 source: git+https://github.com/signal11/hidapi.git
diff --git a/libiio.lwr b/libiio.lwr
index 633072d..30b1325 100644
--- a/libiio.lwr
+++ b/libiio.lwr
@@ -22,7 +22,7 @@ depends:
 - libxml
 - libusb
 description: Library for interfacing with IIO devices
-gitrev: tags/v0.18
+gitrev: tags/v0.21
 inherit: cmake
 satisfy:
   deb: libiio0 >= 0.9 && libiio-dev >= 0.9
diff --git a/libosmo-dsp.lwr b/libosmo-dsp.lwr
index e8e3595..375faa2 100644
--- a/libosmo-dsp.lwr
+++ b/libosmo-dsp.lwr
@@ -30,4 +30,5 @@ inherit: autoconf
 satisfy:
   port: libosmo-dsp
 source: git+https://git.osmocom.org/libosmo-dsp
+mirror: git+https://github.com/osmocom/libosmo-dsp
 installdir: .
diff --git a/libosmocore.lwr b/libosmocore.lwr
index 3818d6a..29aafff 100644
--- a/libosmocore.lwr
+++ b/libosmocore.lwr
@@ -33,5 +33,6 @@ description: A library with generic ulitity functions
developed by Osmocom proje
 gitbranch: master
 inherit: autoconf
 source: git+https://git.osmocom.org/libosmocore
+mirror: git+https://github.com/osmocom/libosmocore
 vars:
   config_opt: ' --disable-libsctp '
diff --git a/rtl-sdr.lwr b/rtl-sdr.lwr
index 27301cc..fb073c4 100644
--- a/rtl-sdr.lwr
+++ b/rtl-sdr.lwr
@@ -30,5 +30,6 @@ satisfy:
   pacman: rtl-sdr
   rpm: rtl-sdr
 source: git+https://git.osmocom.org/rtl-sdr
+mirror: git+https://github.com/osmocom/rtl-sdr
 vars:
   config_opt: ' -DDETACH_KERNEL_DRIVER=ON '

On Thu, May 27, 2021 at 10:59 AM Johannes Demel 
wrote:

> Hi Jeff,
>
> thanks for your help. I decided to be a bit more pragmatic and just
> install the missing piece.
> On Ubuntu 20.04 the required package is `texlive-latex-extra` and
> requires 182 MB of disk space.
>
> All of this is part of my effort to install gr-osmosdr on GR 3.9.
> Besides this hiccup, the pybombs recipe tries to install gr-fcdproplus
> which seems to be stuck with 3.8. This project's CMake output is really
> useful. Anyways, I decided to set gr-fcdproplus to `forceinstalled:
> 'True'` in my prefix config.yml. gr-osmosdr is kind enough to just skip
> this dependency in that case.
>
> Cheers
> Johannes
>
> On 27.05.21 11:32, Jeff Long wrote:
> > Or could just install the missing LaTeX module. On Fedora, it's
> > texlive-newunicodechar. For reference, no problems building libosmo-dsp
> > here.
> >
> > On Thu, May 27, 2021 at 4:21 AM Johannes Demel  > > wrote:
> >
> > Thanks Jeff!
> >
> > Unfortunately, these settings are already present in that
> config.yml. I
> > double checked the config.yml in my prefix as well. There are no
> > overwrites.
> >
> > This is from `gr-recipes/libosmo-dsp.lwr`:
> > ```
> > configure: autoreconf -i -I /usr/share/aclocal && ./configure
> > --prefix=$prefix $config_opt
> > ```
> > I'd really like to learn about `$config_opt`. What value(s) are in
> > there?
> > I removed libosmo-dsp (also from the inventory.yml).
> >
> > This is the output of `pybombs -v install libosmo-dsp`:
> > ```
> > [DEBUG] Requirements met.
> > [DEBUG] Using build directory:
> > /home/johannes/prefix/gnuradio/src/libosmo-dsp
> > [DEBUG] Configuring recipe libosmo-dsp
> > [DEBUG] Using vars - ordereddict([('config_opt', ''), ('builddir',
> > '/home/johannes/prefix/gnuradio/src/libosmo-dsp')])
> > [DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
> > [DEBUG] Executing command `$ autoreconf -i -I /usr/share/aclocal &&
> > ./configure --prefix=/home/johannes/prefix/gnuradio'
> > Configuring: (100%)
> > [DEBUG] Thread signaled termination or returned
> > [DEBUG] Return value: 0
> > [DEBUG] Configure successful.
> > [DEBUG] Setting state to `configured'
> > [DEBUG] Saving inventory to file
> > /home/johannes/prefix/gnuradio/.pybombs/inventory.yml...
> > [DEBUG] Building recipe libosmo-dsp
> > [DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
> > [DEBUG] Executing command `$ make -j64'
> > Building:[
> > ```
> > This is where it hangs.
> >
> > I just tried to run it on a host with a full LaTeX installation.
>

Re: libosmo-dsp build hangs (required for gr-osmosdr)

2021-05-27 Thread Johannes Demel

Hi Jeff,

thanks for your help. I decided to be a bit more pragmatic and just 
install the missing piece.
On Ubuntu 20.04 the required package is `texlive-latex-extra` and 
requires 182 MB of disk space.

All of this is part of my effort to install gr-osmosdr on GR 3.9. 
Besides this hiccup, the pybombs recipe tries to install gr-fcdproplus 
which seems to be stuck with 3.8. This project's CMake output is really 
useful. Anyways, I decided to set gr-fcdproplus to `forceinstalled: 
'True'` in my prefix config.yml. gr-osmosdr is kind enough to just skip 
this dependency in that case.

Cheers
Johannes

On 27.05.21 11:32, Jeff Long wrote:
Or could just install the missing LaTeX module. On Fedora, it's 
texlive-newunicodechar. For reference, no problems building libosmo-dsp 
here.

On Thu, May 27, 2021 at 4:21 AM Johannes Demel > wrote:

Thanks Jeff!

Unfortunately, these settings are already present in that config.yml. I
double checked the config.yml in my prefix as well. There are no
overwrites.

This is from `gr-recipes/libosmo-dsp.lwr`:
```
configure: autoreconf -i -I /usr/share/aclocal && ./configure
--prefix=$prefix $config_opt
```
I'd really like to learn about `$config_opt`. What value(s) are in
there?
I removed libosmo-dsp (also from the inventory.yml).

This is the output of `pybombs -v install libosmo-dsp`:
```
[DEBUG] Requirements met.
[DEBUG] Using build directory:
/home/johannes/prefix/gnuradio/src/libosmo-dsp
[DEBUG] Configuring recipe libosmo-dsp
[DEBUG] Using vars - ordereddict([('config_opt', ''), ('builddir',
'/home/johannes/prefix/gnuradio/src/libosmo-dsp')])
[DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
[DEBUG] Executing command `$ autoreconf -i -I /usr/share/aclocal &&
./configure --prefix=/home/johannes/prefix/gnuradio'
Configuring: (100%)
[DEBUG] Thread signaled termination or returned
[DEBUG] Return value: 0
[DEBUG] Configure successful.
[DEBUG] Setting state to `configured'
[DEBUG] Saving inventory to file
/home/johannes/prefix/gnuradio/.pybombs/inventory.yml...
[DEBUG] Building recipe libosmo-dsp
[DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
[DEBUG] Executing command `$ make -j64'
Building:    [
```
This is where it hangs.

I just tried to run it on a host with a full LaTeX installation. There
it goes through without any issue.

My guess would be that I'd have to do a full LaTeX install. That's
something I'd like to avoid.

I'd like to skip the whole Doxygen part and hope the issue goes away. A
more narrow solution would be nice as well though.

Cheers
Johannes

On 26.05.21 19:17, Jeff Long wrote:
 > In ~/.pybombs/config.yml
 >
 > - config:
 >      makewidth: 4
 >      builddocs: OFF
 >      cmakebuildtype: Release
 >
 > On Wed, May 26, 2021 at 12:41 PM Johannes Demel
mailto:de...@ant.uni-bremen.de>
 > >> wrote:
 >
 >     Hi all,
 >
 >     I'm trying to install gr-osmosdr with GR 3.9. Currently
pybombs hangs
 >     during libosmo-dsp build. Unfortunately it just hangs forever
without
 >     any output, but if I try it manually, I see:
 >
 >     ```
 >     ! LaTeX Error: File `newunicodechar.sty' not found.
 >
 >     Type X to quit or  to proceed,
 >     or enter new name. (Default extension: sty)
 >
 >     Enter file name:
 >     ```
 >     Thus, I'd like to disable generating docs. All of this
happens while
 >     docs are generated. There's a minimal latex install but I
don't want
 >     any
 >     more TeX on that machine.
 >
 >     I can't find the switch to disable docs. How do I do that? Or
disable
 >     doxygen.
 >
 >     Cheers
 >     Johannes
 >
 >     --
 >     Johannes Demel M.Sc.
 >     Research Engineer
 >
 >     University of Bremen
 >     Department of Communications Engineering
 >     Faculty 1 - Physics / Electrical Engineering
 >     NW1, N2400
 >     Otto-Hahn-Allee NW1
 >     28359 Bremen
 >
 >     Phone +49 421 218-62393
 > de...@ant.uni-bremen.de 
>
 >
 >     Secretariat
 >     Tel. +49 421 218-62390
 > pre...@ant.uni-bremen.de 
>
 >
 > www.uni-bremen.de/en 
>
 >
 >     University of Bremen - Established 1971
 >

Re: libosmo-dsp build hangs (required for gr-osmosdr)

2021-05-27 Thread Jeff Long

Or could just install the missing LaTeX module. On Fedora, it's
texlive-newunicodechar. For reference, no problems building libosmo-dsp
here.

On Thu, May 27, 2021 at 4:21 AM Johannes Demel 
wrote:

> Thanks Jeff!
>
> Unfortunately, these settings are already present in that config.yml. I
> double checked the config.yml in my prefix as well. There are no
> overwrites.
>
> This is from `gr-recipes/libosmo-dsp.lwr`:
> ```
> configure: autoreconf -i -I /usr/share/aclocal && ./configure
> --prefix=$prefix $config_opt
> ```
> I'd really like to learn about `$config_opt`. What value(s) are in there?
> I removed libosmo-dsp (also from the inventory.yml).
>
> This is the output of `pybombs -v install libosmo-dsp`:
> ```
> [DEBUG] Requirements met.
> [DEBUG] Using build directory:
> /home/johannes/prefix/gnuradio/src/libosmo-dsp
> [DEBUG] Configuring recipe libosmo-dsp
> [DEBUG] Using vars - ordereddict([('config_opt', ''), ('builddir',
> '/home/johannes/prefix/gnuradio/src/libosmo-dsp')])
> [DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
> [DEBUG] Executing command `$ autoreconf -i -I /usr/share/aclocal &&
> ./configure --prefix=/home/johannes/prefix/gnuradio'
> Configuring: (100%)
> [DEBUG] Thread signaled termination or returned
> [DEBUG] Return value: 0
> [DEBUG] Configure successful.
> [DEBUG] Setting state to `configured'
> [DEBUG] Saving inventory to file
> /home/johannes/prefix/gnuradio/.pybombs/inventory.yml...
> [DEBUG] Building recipe libosmo-dsp
> [DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
> [DEBUG] Executing command `$ make -j64'
> Building:[
> ```
> This is where it hangs.
>
> I just tried to run it on a host with a full LaTeX installation. There
> it goes through without any issue.
>
> My guess would be that I'd have to do a full LaTeX install. That's
> something I'd like to avoid.
>
> I'd like to skip the whole Doxygen part and hope the issue goes away. A
> more narrow solution would be nice as well though.
>
> Cheers
> Johannes
>
> On 26.05.21 19:17, Jeff Long wrote:
> > In ~/.pybombs/config.yml
> >
> > - config:
> >  makewidth: 4
> >  builddocs: OFF
> >  cmakebuildtype: Release
> >
> > On Wed, May 26, 2021 at 12:41 PM Johannes Demel  > > wrote:
> >
> > Hi all,
> >
> > I'm trying to install gr-osmosdr with GR 3.9. Currently pybombs hangs
> > during libosmo-dsp build. Unfortunately it just hangs forever without
> > any output, but if I try it manually, I see:
> >
> > ```
> > ! LaTeX Error: File `newunicodechar.sty' not found.
> >
> > Type X to quit or  to proceed,
> > or enter new name. (Default extension: sty)
> >
> > Enter file name:
> > ```
> > Thus, I'd like to disable generating docs. All of this happens while
> > docs are generated. There's a minimal latex install but I don't want
> > any
> > more TeX on that machine.
> >
> > I can't find the switch to disable docs. How do I do that? Or disable
> > doxygen.
> >
> > Cheers
> > Johannes
> >
> > --
> > Johannes Demel M.Sc.
> > Research Engineer
> >
> > University of Bremen
> > Department of Communications Engineering
> > Faculty 1 - Physics / Electrical Engineering
> > NW1, N2400
> > Otto-Hahn-Allee NW1
> > 28359 Bremen
> >
> > Phone +49 421 218-62393
> > de...@ant.uni-bremen.de 
> >
> > Secretariat
> > Tel. +49 421 218-62390
> > pre...@ant.uni-bremen.de 
> >
> > www.uni-bremen.de/en 
> >
> > University of Bremen - Established 1971
> >
>
>

Re: libosmo-dsp build hangs (required for gr-osmosdr)

2021-05-27 Thread Johannes Demel


Thanks Jeff!

Unfortunately, these settings are already present in that config.yml. I 
double checked the config.yml in my prefix as well. There are no overwrites.


This is from `gr-recipes/libosmo-dsp.lwr`:
```
configure: autoreconf -i -I /usr/share/aclocal && ./configure 
--prefix=$prefix $config_opt

```
I'd really like to learn about `$config_opt`. What value(s) are in there?
I removed libosmo-dsp (also from the inventory.yml).

This is the output of `pybombs -v install libosmo-dsp`:
```
[DEBUG] Requirements met.
[DEBUG] Using build directory: 
/home/johannes/prefix/gnuradio/src/libosmo-dsp

[DEBUG] Configuring recipe libosmo-dsp
[DEBUG] Using vars - ordereddict([('config_opt', ''), ('builddir', 
'/home/johannes/prefix/gnuradio/src/libosmo-dsp')])

[DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
[DEBUG] Executing command `$ autoreconf -i -I /usr/share/aclocal && 
./configure --prefix=/home/johannes/prefix/gnuradio'

Configuring: (100%)
[DEBUG] Thread signaled termination or returned
[DEBUG] Return value: 0
[DEBUG] Configure successful.
[DEBUG] Setting state to `configured'
[DEBUG] Saving inventory to file 
/home/johannes/prefix/gnuradio/.pybombs/inventory.yml...

[DEBUG] Building recipe libosmo-dsp
[DEBUG] In cwd - /home/johannes/prefix/gnuradio/src/libosmo-dsp
[DEBUG] Executing command `$ make -j64'
Building:[
```
This is where it hangs.

I just tried to run it on a host with a full LaTeX installation. There 
it goes through without any issue.


My guess would be that I'd have to do a full LaTeX install. That's 
something I'd like to avoid.


I'd like to skip the whole Doxygen part and hope the issue goes away. A 
more narrow solution would be nice as well though.


Cheers
Johannes

On 26.05.21 19:17, Jeff Long wrote:

In ~/.pybombs/config.yml

- config:
     makewidth: 4
     builddocs: OFF
     cmakebuildtype: Release

On Wed, May 26, 2021 at 12:41 PM Johannes Demel > wrote:


Hi all,

I'm trying to install gr-osmosdr with GR 3.9. Currently pybombs hangs
during libosmo-dsp build. Unfortunately it just hangs forever without
any output, but if I try it manually, I see:

```
! LaTeX Error: File `newunicodechar.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name:
```
Thus, I'd like to disable generating docs. All of this happens while
docs are generated. There's a minimal latex install but I don't want
any
more TeX on that machine.

I can't find the switch to disable docs. How do I do that? Or disable
doxygen.

Cheers
Johannes

-- 
Johannes Demel M.Sc.

Research Engineer

University of Bremen
Department of Communications Engineering
Faculty 1 - Physics / Electrical Engineering
NW1, N2400
Otto-Hahn-Allee NW1
28359 Bremen

Phone +49 421 218-62393
de...@ant.uni-bremen.de 

Secretariat
Tel. +49 421 218-62390
pre...@ant.uni-bremen.de 

www.uni-bremen.de/en 

University of Bremen - Established 1971

query about GRC

2021-05-27 Thread Prof. M.B. Patil




Dear All,

I was not able to figure out how
this works in GRC:

view -> Show block comments

I toggled it, but it did not seem to
make any difference. Any pointers would
be greatly appreciated.

M.Patil

Re: launching gnuradio generated python file core dumps

launching gnuradio generated python file core dumps

Recommendation for PCI-based SDR frontends

Re: Problem changing LO with qt-gui range on Pluto SDR

Problem changing LO with qt-gui range on Pluto SDR

Re: libosmo-dsp build hangs (required for gr-osmosdr)

Re: libosmo-dsp build hangs (required for gr-osmosdr)

Re: libosmo-dsp build hangs (required for gr-osmosdr)

Re: libosmo-dsp build hangs (required for gr-osmosdr)

query about GRC

10 matches

Site Navigation

Mail list logo

Footer information