R: R: R: R: Mpir Installation

[Vincenzo Mone]

Yes Ron,

done another step but now error on the next command make.

I got this:

 

make  all-recursive

make[1]: ingresso nella directory "/home/enzo/mpir"

Making all in tests

make[2]: ingresso nella directory "/home/enzo/mpir/tests"

Making all in .

make[3]: ingresso nella directory "/home/enzo/mpir/tests"

make[3]: Nessuna operazione da eseguire per "all-am".

make[3]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in devel

make[3]: ingresso nella directory "/home/enzo/mpir/tests/devel"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/devel"

Making all in mpn

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpn"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpn"

Making all in fft

make[3]: ingresso nella directory "/home/enzo/mpir/tests/fft"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/fft"

Making all in mpz

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpz"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpz"

Making all in mpq

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpq"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpq"

Making all in mpf

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpf"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpf"

Making all in rand

make[3]: ingresso nella directory "/home/enzo/mpir/tests/rand"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/rand"

Making all in misc

make[3]: ingresso nella directory "/home/enzo/mpir/tests/misc"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/misc"

Making all in cxx

make[3]: ingresso nella directory "/home/enzo/mpir/tests/cxx"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/cxx"

make[2]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in mpn

make[2]: ingresso nella directory "/home/enzo/mpir/mpn"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpn"

Making all in fft

make[2]: ingresso nella directory "/home/enzo/mpir/fft"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/fft"

Making all in mpz

make[2]: ingresso nella directory "/home/enzo/mpir/mpz"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpz"

Making all in mpq

make[2]: ingresso nella directory "/home/enzo/mpir/mpq"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpq"

Making all in mpf

make[2]: ingresso nella directory "/home/enzo/mpir/mpf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpf"

Making all in printf

make[2]: ingresso nella directory "/home/enzo/mpir/printf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/printf"

Making all in scanf

make[2]: ingresso nella directory "/home/enzo/mpir/scanf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/scanf"

Making all in cxx

make[2]: ingresso nella directory "/home/enzo/mpir/cxx"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/cxx"

Making all in tune

make[2]: ingresso nella directory "/home/enzo/mpir/tune"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/tune"

Making all in doc

make[2]: ingresso nella directory "/home/enzo/mpir/doc"

restore=: && backupdir=".am$$" && \

am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \

rm -rf $backupdir && mkdir $backupdir && \

if (/bin/bash /home/enzo/mpir/missing makeinfo --version) >/dev/null 2>&1;
then \

  for f in mpir.info mpir.info-[0-9] mpir.info-[0-9][0-9] mpir.i[0-9]
mpir.i[0-9][0-9]; do \

if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \

  done; \

else :; fi && \

cd "$am__cwd"; \

if /bin/bash /home/enzo/mpir/missing makeinfo   -I . \

-o mpir.info mpir.texi; \

then \

  rc=0; \

  CDPATH="${ZSH_VERSION+.}:" && cd .; \

else \

  rc=$?; \

  CDPATH="${ZSH_VERSION+.}:" && cd . && \

  $restore $backupdir/* `echo "./mpir.info" | sed 's|[^/]*$||'`; \

fi; \

rm -rf $backupdir; exit $rc

/home/enzo/mpir/missing: riga 81: makeinfo: comando non trovato

WARNING: 'makeinfo' is missing on your system.

 You should only need it if you modified a '.texi' file, or

 any other file indirectly affecting the aspect of the manual.

 

Re: Mpir Installation

[Andi Kita]

I looked at Mpir.

Run

./auogen.shThan once that's done and all comes out ok you will run
./configure.

Autogen.sh will bring up configure. It generates the files you need it to
run.
Pretty basic.



On Mon, Apr 27, 2020, 8:29 AM Vincenzo Mone  wrote:

> Hello I am trying to install Mpir on Ubuntu bat get error when I give the
> command ./configure && make && make install
>
> Or just   ./configure .
>
> I have done in terminal:
>
>
>
> git clone git://github.com/wbhart/mpir.git mpir
>
> cd mpir
>
> ./configure
>
>
>
> When I give the last command I get:
>
>
>
> bash: ./configure: File o directory non esistente
>
>
>
> Where  am I missing?
>
> Thanks
>
>
>
> 73 de Enzo IK8OZV
> EasyLog 5 BetaTester
> EasyLog PDA BetaTester
> WinBollet BetaTester
> D.C.I. CheckPoint Regione Campania
> Skype: ik8ozv8520
>
>
>
>
>   *
>
>   **   GSM  +39 328 7110193  **
>
>   * SMS  +39 328 7110193*
>
>   *
>
>
>

Re: R: R: R: R: Mpir Installation

[Ron Economos]

Vincenzo,

I think you're missing libtool.

sudo apt-get install libtool

Then do ./configure again.

If it still fails, e-mail the print out from ./configure.

Ron

On 4/28/20 05:32, Vincenzo Mone wrote:


Yes Ron,

done another step but now error on the next command make.

I got this:

make  all-recursive

make[1]: ingresso nella directory "/home/enzo/mpir"

Making all in tests

make[2]: ingresso nella directory "/home/enzo/mpir/tests"

Making all in .

make[3]: ingresso nella directory "/home/enzo/mpir/tests"

make[3]: Nessuna operazione da eseguire per "all-am".

make[3]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in devel

make[3]: ingresso nella directory "/home/enzo/mpir/tests/devel"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/devel"

Making all in mpn

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpn"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpn"

Making all in fft

make[3]: ingresso nella directory "/home/enzo/mpir/tests/fft"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/fft"

Making all in mpz

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpz"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpz"

Making all in mpq

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpq"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpq"

Making all in mpf

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpf"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpf"

Making all in rand

make[3]: ingresso nella directory "/home/enzo/mpir/tests/rand"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/rand"

Making all in misc

make[3]: ingresso nella directory "/home/enzo/mpir/tests/misc"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/misc"

Making all in cxx

make[3]: ingresso nella directory "/home/enzo/mpir/tests/cxx"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/cxx"

make[2]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in mpn

make[2]: ingresso nella directory "/home/enzo/mpir/mpn"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpn"

Making all in fft

make[2]: ingresso nella directory "/home/enzo/mpir/fft"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/fft"

Making all in mpz

make[2]: ingresso nella directory "/home/enzo/mpir/mpz"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpz"

Making all in mpq

make[2]: ingresso nella directory "/home/enzo/mpir/mpq"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpq"

Making all in mpf

make[2]: ingresso nella directory "/home/enzo/mpir/mpf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpf"

Making all in printf

make[2]: ingresso nella directory "/home/enzo/mpir/printf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/printf"

Making all in scanf

make[2]: ingresso nella directory "/home/enzo/mpir/scanf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/scanf"

Making all in cxx

make[2]: ingresso nella directory "/home/enzo/mpir/cxx"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/cxx"

Making all in tune

make[2]: ingresso nella directory "/home/enzo/mpir/tune"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/tune"

Making all in doc

make[2]: ingresso nella directory "/home/enzo/mpir/doc"

restore=: && backupdir=".am$$" && \

am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \

rm -rf $backupdir && mkdir $backupdir && \

if (/bin/bash /home/enzo/mpir/missing makeinfo --version) >/dev/null 
2>&1; then \


  for f in mpir.info mpir.info-[0-9] mpir.info-[0-9][0-9] mpir.i[0-9] 
mpir.i[0-9][0-9]; do \


    if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \

  done; \

else :; fi && \

cd "$am__cwd"; \

if /bin/bash /home/enzo/mpir/missing makeinfo   -I . \

-o mpir.info mpir.texi; \

then \

  rc=0; \

CDPATH="${ZSH_VERSION+.}:" && cd .; \

else \

  rc=$?; \

CDPATH="${ZSH_VERSION+.}:" && cd . && \

  $restore $backupdir/* `echo "./mpir.info" | sed 's|[^/]*$||'`; \

fi; \

rm -rf $backupdir; exit $rc

/home/enzo/mpir/missing: riga 81: makeinfo: comando non 

Re: Late messages after a tx_time tagged message

[Martin Braun]

Anthony,

the USRP doesn't keep the time, but there is only a single FIFO. If you
schedule 3 messages for sending, they need to be sent in order. Once they
are on the device, they are in a FIFO and will be released in that order.

For example, if have 3 messages A, B, and C. You first send A to be sent at
time T0. Then you send B to be send ASAP. Then you send C to be sent at
time T1 > T0.

A will be sent at T0, but B has to wait for A to clear the FIFO. That means
B will go out at T0 + (length of B).

All our devices have a single FIFO for data, so there's no way around that.
You could try and track the device time in software, and send them to the
device as late as possible, but that's tricky of course.

--M

On Mon, Apr 27, 2020 at 8:58 AM Anthony B.  wrote:

> Hello all,
>
> I am using timed commands to send messages at a specific time, using GNU
> Radio 3.7.14.
> To achieve that, I add a tx_time tag to my message just before the USRP
> Sink, slightly in the future, and it works fine.
> What I'd like to achieve now is to only send specific messages using the
> tx_time tag, in an asynchronous way.
> I just want the other messages to be sent as soon as possible, without
> timed commands.
>
> What happens currently is the following behaviour:
> - the message n is sent successfully, with a tx_time tag
> - the message n+1, without a tx_time tag, is considered late by UHD
> (printing "LL") when it is about to be sent
>
> My interpretation is that the USRP Sink keeps the tx_time tag of the
> message n for all the messages following it.
> Is it possible to clean the tags on the USRP bloc between the messsages n
> and n+1 ?
> Or UHD is only expecting an implementation that updates the tx_time tag
> for the next burst, and so all the messages have to be tagged before being
> sent ?
> Is it possible to mix messages that are timed with the tx_time tag, and in
> the same flow send others that are not ?
>
> Any suggestion would be appreciated.
>
> Best regards,
>
> Anthony
>

R: R: R: R: R: Mpir Installation

[Vincenzo Mone]

Ron,

same error but i have done this:

sudo apt-get install libtool

gone in the Mpir folder and typed:

/configure ( no errors )

Make ( got errors ):

make  all-recursive

make[1]: ingresso nella directory "/home/enzo/mpir"

Making all in tests

make[2]: ingresso nella directory "/home/enzo/mpir/tests"

Making all in .

make[3]: ingresso nella directory "/home/enzo/mpir/tests"

make[3]: Nessuna operazione da eseguire per "all-am".

make[3]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in devel

make[3]: ingresso nella directory "/home/enzo/mpir/tests/devel"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/devel"

Making all in mpn

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpn"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpn"

Making all in fft

make[3]: ingresso nella directory "/home/enzo/mpir/tests/fft"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/fft"

Making all in mpz

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpz"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpz"

Making all in mpq

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpq"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpq"

Making all in mpf

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpf"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpf"

Making all in rand

make[3]: ingresso nella directory "/home/enzo/mpir/tests/rand"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/rand"

Making all in misc

make[3]: ingresso nella directory "/home/enzo/mpir/tests/misc"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/misc"

Making all in cxx

make[3]: ingresso nella directory "/home/enzo/mpir/tests/cxx"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/cxx"

make[2]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in mpn

make[2]: ingresso nella directory "/home/enzo/mpir/mpn"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpn"

Making all in fft

make[2]: ingresso nella directory "/home/enzo/mpir/fft"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/fft"

Making all in mpz

make[2]: ingresso nella directory "/home/enzo/mpir/mpz"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpz"

Making all in mpq

make[2]: ingresso nella directory "/home/enzo/mpir/mpq"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpq"

Making all in mpf

make[2]: ingresso nella directory "/home/enzo/mpir/mpf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpf"

Making all in printf

make[2]: ingresso nella directory "/home/enzo/mpir/printf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/printf"

Making all in scanf

make[2]: ingresso nella directory "/home/enzo/mpir/scanf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/scanf"

Making all in cxx

make[2]: ingresso nella directory "/home/enzo/mpir/cxx"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/cxx"

Making all in tune

make[2]: ingresso nella directory "/home/enzo/mpir/tune"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/tune"

Making all in doc

make[2]: ingresso nella directory "/home/enzo/mpir/doc"

restore=: && backupdir=".am$$" && \

am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \

rm -rf $backupdir && mkdir $backupdir && \

if (/bin/bash /home/enzo/mpir/missing makeinfo --version) >/dev/null 2>&1;
then \

  for f in mpir.info mpir.info-[0-9] mpir.info-[0-9][0-9] mpir.i[0-9]
mpir.i[0-9][0-9]; do \

if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \

  done; \

else :; fi && \

cd "$am__cwd"; \

if /bin/bash /home/enzo/mpir/missing makeinfo   -I . \

-o mpir.info mpir.texi; \

then \

  rc=0; \

  CDPATH="${ZSH_VERSION+.}:" && cd .; \

else \

  rc=$?; \

  CDPATH="${ZSH_VERSION+.}:" && cd . && \

  $restore $backupdir/* `echo "./mpir.info" | sed 's|[^/]*$||'`; \

fi; \

rm -rf $backupdir; exit $rc

/home/enzo/mpir/missing: riga 81: makeinfo: comando non trovato

WARNING: 'makeinfo' is missing on your system.

 You should only need it if you modified a '.texi' file, or

 any 

Re: R: R: R: R: R: Mpir Installation

[Ron Economos]

It's not building any of the directories, so the ./configure step must 
have problems. Please post the results of ./configure.


Ron

On 4/28/20 08:57, Vincenzo Mone wrote:


Ron,

same error but i have done this:

sudo apt-get install libtool

gone in the Mpir folder and typed:

/configure ( no errors )

Make ( got errors ):

make  all-recursive

make[1]: ingresso nella directory "/home/enzo/mpir"

Making all in tests

make[2]: ingresso nella directory "/home/enzo/mpir/tests"

Making all in .

make[3]: ingresso nella directory "/home/enzo/mpir/tests"

make[3]: Nessuna operazione da eseguire per "all-am".

make[3]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in devel

make[3]: ingresso nella directory "/home/enzo/mpir/tests/devel"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/devel"

Making all in mpn

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpn"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpn"

Making all in fft

make[3]: ingresso nella directory "/home/enzo/mpir/tests/fft"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/fft"

Making all in mpz

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpz"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpz"

Making all in mpq

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpq"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpq"

Making all in mpf

make[3]: ingresso nella directory "/home/enzo/mpir/tests/mpf"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/mpf"

Making all in rand

make[3]: ingresso nella directory "/home/enzo/mpir/tests/rand"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/rand"

Making all in misc

make[3]: ingresso nella directory "/home/enzo/mpir/tests/misc"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/misc"

Making all in cxx

make[3]: ingresso nella directory "/home/enzo/mpir/tests/cxx"

make[3]: Nessuna operazione da eseguire per "all".

make[3]: uscita dalla directory "/home/enzo/mpir/tests/cxx"

make[2]: uscita dalla directory "/home/enzo/mpir/tests"

Making all in mpn

make[2]: ingresso nella directory "/home/enzo/mpir/mpn"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpn"

Making all in fft

make[2]: ingresso nella directory "/home/enzo/mpir/fft"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/fft"

Making all in mpz

make[2]: ingresso nella directory "/home/enzo/mpir/mpz"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpz"

Making all in mpq

make[2]: ingresso nella directory "/home/enzo/mpir/mpq"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpq"

Making all in mpf

make[2]: ingresso nella directory "/home/enzo/mpir/mpf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/mpf"

Making all in printf

make[2]: ingresso nella directory "/home/enzo/mpir/printf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/printf"

Making all in scanf

make[2]: ingresso nella directory "/home/enzo/mpir/scanf"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/scanf"

Making all in cxx

make[2]: ingresso nella directory "/home/enzo/mpir/cxx"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/cxx"

Making all in tune

make[2]: ingresso nella directory "/home/enzo/mpir/tune"

make[2]: Nessuna operazione da eseguire per "all".

make[2]: uscita dalla directory "/home/enzo/mpir/tune"

Making all in doc

make[2]: ingresso nella directory "/home/enzo/mpir/doc"

restore=: && backupdir=".am$$" && \

am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \

rm -rf $backupdir && mkdir $backupdir && \

if (/bin/bash /home/enzo/mpir/missing makeinfo --version) >/dev/null 
2>&1; then \


  for f in mpir.info mpir.info-[0-9] mpir.info-[0-9][0-9] mpir.i[0-9] 
mpir.i[0-9][0-9]; do \


    if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \

  done; \

else :; fi && \

cd "$am__cwd"; \

if /bin/bash /home/enzo/mpir/missing makeinfo   -I . \

-o mpir.info mpir.texi; \

then \

  rc=0; \

CDPATH="${ZSH_VERSION+.}:" && cd .; \

else \

  rc=$?; \

CDPATH="${ZSH_VERSION+.}:" && cd . && \

  $restore $backupdir/* `echo "./mpir.info" | sed 's|[^/]*$||'`; \

fi; \

rm -rf $backupdir; exit $rc

Hidden e-mail address

[Artur Nogueira]

Hello all,

I was recently looking for some specific topics on https://lists.gnu.org/ and
I realized that many e-mail addresses appear like address@hidden there.
How do I do to get my e-mail address hidden in the same way?

Best regards,
Artur

Re: Mpir Installation

[Chris Vine]

On Tue, 28 Apr 2020 17:57:36 +0200
"Vincenzo Mone"  wrote:
> WARNING: 'makeinfo' is missing on your system.
> 
>  You should only need it if you modified a '.texi' file, or
> 
>  any other file indirectly affecting the aspect of the manual.
> 
>  You might want to install the Texinfo package:
> 
>  
> 
>  The spurious makeinfo call might also be the consequence of
> 
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
> 
>  want to install GNU make:
> 
>  
> 
> Makefile:403: recipe for target 'mpir.info' failed
> 
> make[2]: *** [mpir.info] Error 127
> 
> make[2]: uscita dalla directory "/home/enzo/mpir/doc"
> 
> Makefile:952: recipe for target 'all-recursive' failed
> 
> make[1]: *** [all-recursive] Error 1
> 
> make[1]: uscita dalla directory "/home/enzo/mpir"
> 
> Makefile:755: recipe for target 'all' failed
> 
> make: *** [all] Error 2
> 
> Did I done something wrong?
> 
> Thanks

You are doing lots wrong.

First you are missing texinfo's makeinfo, which seems to be used by mpir
to make its documentation.  That's fine, you don't need texinfo.

Secondly, you don't need texinfo because you are pointlessly trying to
compile and install mpir.  Why?  Your distribution will already come
with gmp or mpir so it is completely unnecessary.

Thirdly, you are posting massively long posts with no regard for
snipping irrelevant content.

Fourthly, trying to install these out-of-distribution packages, when
your distribution will already provide them, is going to break your
installation.  You will end up with conflicting and incompatible
versions of different libraries installed.

I suggest deleting your current linux installation, reinstall it from
scratch, and install that distribution's version of gnuradio.  You are
way out of your depth.

Re: Weird Python Sinks Crash with GNU Radio 3.8.1

[Christophe Seguinot]

  
  
Hi 

It crashes with a Segmentation fault (core dumped)

  Ubuntu 18.04
  GNURadio 3.8.1 
  



On 28/04/2020 07:07, Gilad Beeri
  (ApolloShield) wrote:


  
  
Hi,
Can someone
  with GNU Radio 3.8.1 and Python 3.8 on Linux run the attached
  file and check if it crashes?


I get
  persistent results over several computers for a crash on that
  setup, while it is ok on Python 2.7 and GNU Radio 3.7.11.


  
  ᐧ
  
  
On Sun, Apr 26, 2020 at 11:19
  AM Gilad Beeri (ApolloShield) 
  wrote:


  
Hi,
I
  succeeded in narrowing down the flowgraph to a minimal
  graph that reproduces the issue. You can see the Python
  file attached.


Basically,
  when having a file source that feeds 2 different Null
  Python Sinks", the process crashes with a seg fault, with
  the same stack trace I showed before:



  include/gnuradio/py_feval.h:69 which
is py_eval_ll::calleval(int):
  return
  eval(x);
  

The
  flowgraph is very simple:
File
  Source -> Python Null Sink - 2 times


Replacing
  one of the Null Python Sinks to a standard Null Sink
  "solves" the issue - the crash doesn't reproduce. You can
  comment-in line 43 and comment-out line 44 to witness
  that.
I used
  the same file source block but I also tested it with 2
  different file sources and it behaves the same.


Any ideas
  why does this happen in GNU Radio 3.8.1?


  
  ᐧ
  
  
On Thu, Apr 23, 2020 at
  6:50 PM Gilad Beeri (ApolloShield) 
  wrote:


  
I
  have a rather complex flowgraph that used to work well
  with GNU Radio 3.7.

I
  upgraded to 3.8.1, and now it crashes (for some input,
  but even when I use /dev/zero as file source) with
  something that looks like in the core of GNU Radio
  (not directly in the block).



  
Environment:

GNU Radio 3.8.1
Python 3.8.2
Ubuntu 16.04.6


  

There
  are many blocks, but let's focus on the last ones.
I
  have a float-to-int block (the standard one) which
  feeds data into a sink block that is written in
  Python. In case it is relevant, this is the block that
  feeds the sink:         float_to_int =
blocks.float_to_int(); self.connect(float_to_int,
sink)


The
  process crashes with a segmentation fault.


If I
  nullify the Python sink (commenting out all real
  processing code in work()), the issue still happens.
Furthermore,
  I wrote a "my_null_sink" block in Python (see code
  below). It still crashes with the same issue (after I
  connected it to the float-to-int output instead of the
  original Python sink).
When
  I replace "my_null_sink" with GNU Radio's standard
  Null Sink, it doesn't crash anymore.
Using
  the same input file and my_null_sink, it crashes about
  95% of the runs (i.e., not 100%, but almost always),
  with Null Sink, 0%.
That's
  why I believe it is something with the Python binding.
  I do have other Python blocks in the flowgraph (one
  that is connected to the file source and does some
  simple processing before passing forward the samples).


When
  I run it with gdb, I catch the exception and the stack
  trace is below.
The
  2nd frame in the stack sends us to block_gateway_impl.cc:139,

Re: R: R: Mpir Installation

[Ron Economos]

Looks like you're missing M4. Try:

sudo apt-get install autotools-dev automake autoconf

For reference, here's what I'm seeing.

ubuntu@arm:~/xfer/mpir$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize
libtoolize: putting auxiliary files in '.'.
libtoolize: linking file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --no-force
configure.ac:1719: installing './compile'
configure.ac:57: installing './config.guess'
configure.ac:57: installing './config.sub'
configure.ac:67: installing './install-sh'
configure.ac:67: installing './missing'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `.'

Ron

On 4/28/20 03:35, Vincenzo Mone wrote:


Ron,

please this morning I have retried again doing these steps:

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

But I seem to get errors:

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is 
m4_require'd but not m4_defun'd


acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

autoreconf: configure.ac: tracing

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is 
m4_require'd but not m4_defun'd


acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

autoreconf: configure.ac: not using Libtool

autoreconf: running: /usr/bin/autoconf

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is 
m4_require'd but not m4_defun'd


acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not 
m4_defun'd


acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure:11016: error: possibly undefined macro: AC_PROG_NM

  If this token and others are legitimate, please use 
m4_pattern_allow.


  See the Autoconf documentation.

configure:14470: error: possibly undefined macro: 
AC_LIBTOOL_PROG_COMPILER_PIC


configure:14565: error: possibly undefined macro: AC_ENABLE_SHARED

configure:14566: error: possibly undefined macro: AC_PROG_LIBTOOL

autoreconf: /usr/bin/autoconf failed with exit status: 1

If I continue with the next command:

./configure

I get

configure: error: cannot find install-sh, install.sh, or shtool in "." 
"./.." "./../.."


Please what am I doing wrong?

Thanks

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




*

** GSM  +39 328 7110193  **

  * SMS  +39 328 7110193 *

  *

*Da:*Ron Economos 
*Inviato:* lunedì 27 aprile 2020 15:18
*A:* Vincenzo Mone 
*Oggetto:* Re: R: Mpir Installation

Vincenzo,

I see. You have to create the ./configure file in mpir with ./autogen.sh

So it's really these steps:

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

./configure

make

sudo make install

sudo ldconfig

Ron W6RZ

On 4/27/20 05:56, Vincenzo Mone wrote:

Thanks Ron,

But I cannot get installed FCDPROPLUS.

I have done this:

git clone https://github.com/dl1ksv/gr-fcdproplus

cd gr-fcdproplus

mkdir build

cd build

make -DCMAKE_INSTALL_PREFIX= \usr ../

-- Build type not specified: defaulting to release.

-- Checking for module 'mpir >= 3.0'

--   No package 'mpir' found

-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY
MPIR_INCLUDE_DIR)

-- User set python executable /usr/bin/python3

-- Found 

R: R: Mpir Installation

[Vincenzo Mone]

Ron,

please this morning I have retried again doing these steps:

 

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

 

But I seem to get errors:

 

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal 

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but
not m4_defun'd

acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

autoreconf: configure.ac: tracing

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but
not m4_defun'd

acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

autoreconf: configure.ac: not using Libtool

autoreconf: running: /usr/bin/autoconf

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but
not m4_defun'd

acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: warning: AC_PROG_LIBTOOL is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure:11016: error: possibly undefined macro: AC_PROG_NM

  If this token and others are legitimate, please use m4_pattern_allow.

  See the Autoconf documentation.

configure:14470: error: possibly undefined macro:
AC_LIBTOOL_PROG_COMPILER_PIC

configure:14565: error: possibly undefined macro: AC_ENABLE_SHARED

configure:14566: error: possibly undefined macro: AC_PROG_LIBTOOL

autoreconf: /usr/bin/autoconf failed with exit status: 1

 

If I continue with the next command:

 

./configure

 

I get 

configure: error: cannot find install-sh, install.sh, or shtool in "."
"./.." "./../.."

 

 

Please what am I doing wrong?

Thanks

 

 

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *

  **   GSM  +39 328 7110193  **

  * SMS  +39 328 7110193*

  *

 

Da: Ron Economos  
Inviato: lunedì 27 aprile 2020 15:18
A: Vincenzo Mone 
Oggetto: Re: R: Mpir Installation

 

Vincenzo,

I see. You have to create the ./configure file in mpir with ./autogen.sh

So it's really these steps:

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

./configure

make

sudo make install

sudo ldconfig

Ron W6RZ

On 4/27/20 05:56, Vincenzo Mone wrote:

Thanks Ron,

But I cannot get installed FCDPROPLUS.

I have done this:

 

git clone https://github.com/dl1ksv/gr-fcdproplus

cd gr-fcdproplus

mkdir build

cd build

make -DCMAKE_INSTALL_PREFIX= \usr ../

-- Build type not specified: defaulting to release.

-- Checking for module 'mpir >= 3.0'

--   No package 'mpir' found

-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY
MPIR_INCLUDE_DIR) 

-- User set python executable /usr/bin/python3

-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found
suitable exact version "3.8.2") 

-- Found ALSA 1.2.2

-- Found jack: /usr/lib/x86_64-linux-gnu/libjack.so

-- Extracting version information from git describe...

-- 

-- Checking for module SWIG

-- Found SWIG version 4.0.1.

-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found
version "3.8.2") 

-- Doxxyfile found in DOXY_FILE_PATH-NOTFOUND

CMake Error: File
/home/enzo/gr-fcdproplus/swig/DOXY_FILE_PATH-NOTFOUND/Doxyfile.swig_doc.in
does not exist.

CMake Error at cmake/Modules/GrSwig.cmake:65 (configure_file):

  configure_file Problem configuring file

Call Stack (most recent call first):

  cmake/Modules/GrSwig.cmake:121 (GR_SWIG_MAKE_DOCS)

  swig/CMakeLists.txt:41 (GR_SWIG_MAKE)

 

 

CMake Error: File
/home/enzo/gr-fcdproplus/docs/doxygen/DOXY_FILE_PATH-NOTFOUND/Doxyfile.in
does not exist.

CMake Error at docs/doxygen/CMakeLists.txt:33 (configure_file):

  configure_file Problem configuring file

 

 

--  Build Summary =

-- Building gr-fcdproplus  : 3.8.0 for Linux 

-- Building 

Re: Weird Python Sinks Crash with GNU Radio 3.8.1

[Marcus Müller]

Sadly, I can reproduce this, too, but only on 3.8; hm.

On 28.04.20 07:59, Christophe Seguinot wrote:
> Hi
> 
> It crashes with a Segmentation fault (core dumped)
> 
>   * Ubuntu 18.04
>   * GNURadio 3.8.1
> 
> 
> On 28/04/2020 07:07, Gilad Beeri (ApolloShield) wrote:
>> Hi,
>> Can someone with GNU Radio 3.8.1 and Python 3.8 on Linux run the
>> attached file and check if it crashes?
>>
>> I get persistent results over several computers for a crash on that
>> setup, while it is ok on Python 2.7 and GNU Radio 3.7.11.
>>
>> ᐧ
>>
>> On Sun, Apr 26, 2020 at 11:19 AM Gilad Beeri (ApolloShield)
>> mailto:gi...@apolloshield.com>> wrote:
>>
>> Hi,
>> I succeeded in narrowing down the flowgraph to a minimal graph
>> that reproduces the issue. You can see the Python file attached.
>>
>> Basically, when having a file source that feeds 2 different Null
>> Python Sinks", the process crashes with a seg fault, with the same
>> stack trace I showed before:
>>
>> /include/gnuradio/py_feval.h:69/ which is /py_eval_ll::calleval(int)/:
>> /return eval(x);/
>>
>> The flowgraph is very simple:
>> File Source -> Python Null Sink - 2 times
>>
>> Replacing one of the Null Python Sinks to a standard Null Sink
>> "solves" the issue - the crash doesn't reproduce. You can
>> comment-in line 43 and comment-out line 44 to witness that.
>> I used the same file source block but I also tested it with 2
>> different file sources and it behaves the same.
>>
>> Any ideas why does this happen in GNU Radio 3.8.1?
>>
>> ᐧ
>>
>> On Thu, Apr 23, 2020 at 6:50 PM Gilad Beeri (ApolloShield)
>> mailto:gi...@apolloshield.com>> wrote:
>>
>> I have a rather complex flowgraph that used to work well with
>> GNU Radio 3.7.
>> I upgraded to 3.8.1, and now it crashes (for some input, but
>> even when I use /dev/zero as file source) with something that
>> looks like in the core of GNU Radio (not directly in the block).
>>
>> Environment:
>> GNU Radio 3.8.1
>> Python 3.8.2
>> Ubuntu 16.04.6
>>
>> There are many blocks, but let's focus on the last ones.
>> I have a float-to-int block (the standard one) which feeds
>> data into a sink block that is written in Python. In case it
>> is relevant, this is the block that feeds the sink:       
>>  /float_to_int =
>> blocks.float_to_int(); self.connect(float_to_int, sink)/
>>
>> The process crashes with a segmentation fault.
>>
>> If I nullify the Python sink (commenting out all real
>> processing code in work()), the issue still happens.
>> Furthermore, I wrote a "my_null_sink" block in Python (see
>> code below). It still crashes with the same issue (after I
>> connected it to the float-to-int output instead of the
>> original Python sink).
>> When I replace "my_null_sink" with GNU Radio's standard Null
>> Sink, it doesn't crash anymore.
>> Using the same input file and my_null_sink, it crashes about
>> 95% of the runs (i.e., not 100%, but almost always), with Null
>> Sink, 0%.
>> That's why I believe it is something with the Python binding.
>> I do have other Python blocks in the flowgraph (one that is
>> connected to the file source and does some simple processing
>> before passing forward the samples).
>>
>> When I run it with gdb, I catch the exception and the stack
>> trace is below.
>> The 2nd frame in the stack sends us
>> to /block_gateway_impl.cc:139/, work(), 
>> /_handler->calleval(0);/
>> The 1st stack frame doesn't have an associated module for the
>> specified address (0x02324b90 in ??), "i sh" shows it
>> isn't associated with any module, and "info symbol "
>> confirms this. I also witness that all modules are loaded into
>> addresses > 0x7f13, so I assume the address from
>> the stack trace is really not a valid library, but some
>> garbage (it's also very close to 0).
>> The faulty memory address tends to change which is another
>> indication for garbage.
>>
>> Note: when I build the app in Debug, another stack frame
>> appears between the one that isn't associated with a module,
>> to the one in block_gateway_impl:
>> /include/gnuradio/py_feval.h:69/ which is
>> /py_eval_ll::calleval(int)/:
>> /return eval(x);/
>> /
>> /
>> When I implement the simplest flowgraph: File Source with
>> /dev/zero -> Throttle -> my_null_sink, it doesn't crash.
>>
>> In the original flowgraph, I disabled almost all blocks, and
>> specifically, I did not leave any enabled own C++ block - just
>> to rule out the possibility that one of the blocks corrupts
>> the 

Re: R: Again on FCDPROPLUS

[Sid Boyce]

The destination is missing, the file 99-usb-serial.rules file  needs to 
be copied to /etc/udev/rules./


sudo cp -v ~/Desktop/enzo/99-usb-serial.rules /etc/udev/rules.d/
73 ... Sid.

On 28/04/2020 09:53, Vincenzo Mone wrote:

Hello Barry,
Thanks also to you for the help, but the problem is everyone is trying to
help me
Saying what to do as I know how Linux works.
Unfortunately I am a beginner user and do not know anything about Linux.
Just starting and following all you suggestions but the problem is I do not
understand
What to do if some says for example start as administrator as how I saw it
is different from windows O.S.

BTW I have tried how you suggested me but it did not work maybe because how
I said before
Did not do correctly the commands.
Here is what I've done:
I have opened the Terminal and typed gedit which is the editor.
Pasted the 4 lines.
Closed the file saving it in Enzo which is the folder I see on the Desktop
Always in the terminal I have typed:

sudo cp -v ~/Desktop/enzo/99-usb-serial.rules

but after have inserted the requested password I got the error:


cp: missing destination file operand after
'/home/enzo/Desktop/enzo/99-usb-serial.rules'

Where am I still missing?

Finally you said to be sure to set the Device name; mine is
"hw:CARD=V20,DEV=0"
How to know the Device name?
I can just say that it is a Funcube Dongle Pro Plus.
Thanks to you and to everyone and please apologise if I am bothering
somebody


73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




   *
   **   GSM  +39 328 7110193  **
   * SMS  +39 328 7110193    *
   *


-Messaggio originale-
Da: Barry Duggan 
Inviato: martedì 28 aprile 2020 01:48
A: vim...@alice.it
Cc: Discuss Gnuradio 
Oggetto: Re: Again on FCDPROPLUS

Vincenzo,

Here is what you need to do to set up udev rules:

In any of your folders (), create a file named '99-usb-
serial.rules' with the following content:

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31"
MODE:="0666"

Save the file. Then, in a Terminal screen:

cd /etc/udev/rules.d
sudo cp -v ~//99-usb-serial.rules .  # note the
period!
sudo udevadm trigger

Be sure to set the Device name; mine is "hw:CARD=V20,DEV=0" (without the
quotes). If that doesn't work, follow the procedure in
https://wiki.gnuradio.org/index.php/Audio_Source#Device_Name starting
with "For Linux ALSA users...".

Let me know how it works for you.
--
Barry Duggan KV4FV

On Sun, 26 Apr 2020 18:29:17 +0200, Vincenzo Mone wrote:

Hello,

Please I have a doubt.

Reading on the FCDPROPLUS site I read:

Important
Don't forget the udev rules: For instance:

Udev rules for the Funcube Dongle Pro (0xfb56) and Pro+ (0xfb31)

HIDAPI/libusb:

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56"
MODE:="0666" SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"
ATTRS{idProduct}=="fb31" MODE:="0666"

HIDAPI/hidraw:

KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb56", MODE="0666" KERNEL=="hidraw*",
ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb31",
MODE="0666

Please what does it means?

Maybe I am missing something.

Any help?

Thanks

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: R: Gnuradio 3.7

[Johannes Demel]

Hi Vincenzo,

please reply on list. Every mail client is configurable to make this 
task easier for you. I recommend you search for the correct settings for 
your client.


Regarding use of GR 3.7. I suggest you ask yourself the following questions:

- Did you use GNU Radio before? No? -> use GR 3.8
- Are you willing to fight your way through with old software and old 
dependencies?


If you'd come to the conclusion that you really need a Linux distro with 
Python2 support, I'd recommend you choose one with long term support. 
e.g. Ubuntu 18.04LTS. Ubuntu 19.10 will drop out of support around July. 
At that point you shouldn't use this system at all.


Using older systems is really something you should only ever consider if 
you know the pros and cons on a technical level. Otherwise you lack all 
the newer features and improvements while it always becomes harder to 
find support and help.
I assume most developers that can help you with any project are really 
eager to use the latest versions of distros, compilers etc. because they 
want to use the latest features. To most of them legacy support is no 
fun. That's another great argument in favor of using the latest GNU 
Radio version as well.


Cheers
Johannes


On 27.04.20 12:53, Vincenzo Mone wrote:

Hello Johannes,
thanks for your reply.
I have also the 19.10 version.
Can I use this one or you definitely suggest me to find the 18.04 one?
Then how to get the Gnuradio 3.7?
Thanks

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




   *
   **   GSM  +39 328 7110193  **
   * SMS  +39 328 7110193    *
   *


-Messaggio originale-
Da: Discuss-gnuradio 
Per conto di Johannes Demel
Inviato: lunedì 27 aprile 2020 09:45
A: discuss-gnuradio@gnu.org
Oggetto: Re: Gnuradio 3.7

Hi Vincenzo,

one major change in Ubuntu 20.04 is: Python 2 is removed. "Long live

Python

3+!" [0] Theoretically you could re-enable it but this is discouraged.

One major change for GNU Radio 3.8 is Python 3 support for exactly this
reason. Python2 is dead effective 2020-01-01. We had 10 years to port
everything from 2 to 3.
Also, Qt will probably be tricky too but that's just a guess.

So, if you want to (or have to) use GNU Radio 3.7, stick with Ubuntu

18.04.

This would be the reasonable approach. If you'd want to use an OOT module
that was not ported to 3.8, now might be a good time to port it.

Cheers
Johannes


[0]
https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-
python-2.html

On 26.04.20 15:25, Vincenzo Mone wrote:

Please I own the UBUNTU 20.04 LTS.

I do not want to use the latest 3.8 Gnuradio-Companion but

I would like to install the 3.7 version.

Please anybody can point me step by step how to do?

Thanks

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




    *

**   GSM  +39 328 7110193  **

    * SMS  +39 328 7110193    *

    *

Re: Gnuradio 3.7

[Adrian Musceac]

With gnuradio Qt is a bigger problem than Python, with some distro packages 
using qt4, others using qt5. 

On April 27, 2020 7:44:48 AM UTC, Johannes Demel  
wrote:
>Hi Vincenzo,
>
>one major change in Ubuntu 20.04 is: Python 2 is removed. "Long live 
>Python 3+!" [0] Theoretically you could re-enable it but this is 
>discouraged.
>
>One major change for GNU Radio 3.8 is Python 3 support for exactly this
>
>reason. Python2 is dead effective 2020-01-01. We had 10 years to port 
>everything from 2 to 3.
>Also, Qt will probably be tricky too but that's just a guess.
>
>So, if you want to (or have to) use GNU Radio 3.7, stick with Ubuntu 
>18.04. This would be the reasonable approach. If you'd want to use an 
>OOT module that was not ported to 3.8, now might be a good time to port
>it.
>
>Cheers
>Johannes
>
>
>[0] 
>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html
>
>On 26.04.20 15:25, Vincenzo Mone wrote:
>> Please I own the UBUNTU 20.04 LTS.
>> 
>> I do not want to use the latest 3.8 Gnuradio-Companion but
>> 
>> I would like to install the 3.7 version.
>> 
>> Please anybody can point me step by step how to do?
>> 
>> Thanks
>> 
>> 73 de Enzo IK8OZV
>> EasyLog 5 BetaTester
>> EasyLog PDA BetaTester
>> WinBollet BetaTester
>> D.C.I. CheckPoint Regione Campania
>> Skype: ik8ozv8520
>> 
>> 
>> 
>> 
>>    *
>> 
>> **   GSM  +39 328 7110193  **
>> 
>>    * SMS  +39 328 7110193    *
>> 
>>    *
>> 

R: Again on FCDPROPLUS

[Vincenzo Mone]

Hello Barry,
Thanks also to you for the help, but the problem is everyone is trying to
help me
Saying what to do as I know how Linux works.
Unfortunately I am a beginner user and do not know anything about Linux.
Just starting and following all you suggestions but the problem is I do not
understand
What to do if some says for example start as administrator as how I saw it
is different from windows O.S.

BTW I have tried how you suggested me but it did not work maybe because how
I said before 
Did not do correctly the commands.
Here is what I've done:
I have opened the Terminal and typed gedit which is the editor.
Pasted the 4 lines.
Closed the file saving it in Enzo which is the folder I see on the Desktop
Always in the terminal I have typed:

sudo cp -v ~/Desktop/enzo/99-usb-serial.rules

but after have inserted the requested password I got the error:


cp: missing destination file operand after
'/home/enzo/Desktop/enzo/99-usb-serial.rules'

Where am I still missing?

Finally you said to be sure to set the Device name; mine is
"hw:CARD=V20,DEV=0"
How to know the Device name?
I can just say that it is a Funcube Dongle Pro Plus.
Thanks to you and to everyone and please apologise if I am bothering
somebody


73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *
  **   GSM  +39 328 7110193  **
  * SMS  +39 328 7110193    *
  *

> -Messaggio originale-
> Da: Barry Duggan 
> Inviato: martedì 28 aprile 2020 01:48
> A: vim...@alice.it
> Cc: Discuss Gnuradio 
> Oggetto: Re: Again on FCDPROPLUS
> 
> Vincenzo,
> 
> Here is what you need to do to set up udev rules:
> 
> In any of your folders (), create a file named '99-usb-
> serial.rules' with the following content:
> 
> SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31"
> MODE:="0666"
> 
> Save the file. Then, in a Terminal screen:
> 
>cd /etc/udev/rules.d
>sudo cp -v ~//99-usb-serial.rules .  # note the
> period!
>sudo udevadm trigger
> 
> Be sure to set the Device name; mine is "hw:CARD=V20,DEV=0" (without the
> quotes). If that doesn't work, follow the procedure in
> https://wiki.gnuradio.org/index.php/Audio_Source#Device_Name starting
> with "For Linux ALSA users...".
> 
> Let me know how it works for you.
> --
> Barry Duggan KV4FV
> 
> On Sun, 26 Apr 2020 18:29:17 +0200, Vincenzo Mone wrote:
> 
> Hello,
> 
> Please I have a doubt.
> 
> Reading on the FCDPROPLUS site I read:
> 
> Important
> Don't forget the udev rules: For instance:
> 
> Udev rules for the Funcube Dongle Pro (0xfb56) and Pro+ (0xfb31)
> 
> HIDAPI/libusb:
> 
> SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56"
> MODE:="0666" SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"
> ATTRS{idProduct}=="fb31" MODE:="0666"
> 
> HIDAPI/hidraw:
> 
> KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
> ATTRS{idProduct}=="fb56", MODE="0666" KERNEL=="hidraw*",
> ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
> ATTRS{idProduct}=="fb31",
> MODE="0666
> 
> Please what does it means?
> 
> Maybe I am missing something.
> 
> Any help?
> 
> Thanks
> 
> 73 de Enzo IK8OZV
> EasyLog 5 BetaTester
> EasyLog PDA BetaTester
> WinBollet BetaTester
> D.C.I. CheckPoint Regione Campania
> Skype: ik8ozv8520

R: R: R: Mpir Installation

[Vincenzo Mone]

Yes Ron,

it waorked since i gave the ./configure command.

I got another error:

 

checking build system type... x86_64-unknown-linux-gnu

checking host system type... x86_64-unknown-linux-gnu

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... no

checking for mawk... mawk

checking whether make sets $(MAKE)... yes

checking whether make supports nested variables... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking ABI=64

checking compiler gcc -m64 ... yes

checking compiler gcc -m64  -O2... yes

checking compiler gcc -m64 -O2  -march=k8... yes

checking compiler gcc -m64 -O2 -march=k8  -mtune=k8... yes

checking for gcc... gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables... 

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking whether gcc understands -c and -o together... yes

checking how to run the C preprocessor... gcc -E

checking for grep that handles long lines and -e... /bin/grep

checking for egrep... /bin/grep -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking minix/config.h usability... no

checking minix/config.h presence... no

checking for minix/config.h... no

checking whether it is safe to define __EXTENSIONS__... yes

checking for gcc... (cached) gcc

checking whether we are using the GNU C compiler... (cached) yes

checking whether gcc accepts -g... (cached) yes

checking for gcc option to accept ISO C89... (cached) none needed

checking whether gcc understands -c and -o together... (cached) yes

checking for gcc option to accept ISO C99... none needed

checking for gcc option to accept ISO Standard C... (cached) none needed

checking how to run the C preprocessor... gcc -E

checking build system compiler gcc... yes

checking for build system preprocessor... gcc -E

checking for build system executable suffix... 

checking whether build system compiler is ANSI... yes

checking for build system compiler math library... -lm

Looking for a system-wide yasm...

configure: error: no system-wide yasm found

 

What am I still missing please?

Thanks

 

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *

  **   GSM  +39 328 7110193  **

  * SMS  +39 328 7110193*

  *

 

Da: Discuss-gnuradio  Per
conto di Ron Economos
Inviato: martedì 28 aprile 2020 13:00
A: discuss-gnuradio@gnu.org
Oggetto: Re: R: R: Mpir Installation

 

Looks like you're missing M4. Try:

sudo apt-get install autotools-dev automake autoconf

For reference, here's what I'm seeing.

ubuntu@arm:~/xfer/mpir$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal 
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize
libtoolize: putting auxiliary files in '.'.
libtoolize: linking file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --no-force
configure.ac:1719: installing './compile'
configure.ac:57: installing './config.guess'
configure.ac:57: installing './config.sub'
configure.ac:67: installing './install-sh'
configure.ac:67: installing './missing'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `.'

Ron

On 4/28/20 03:35, Vincenzo Mone wrote:

Ron,

please this morning I have retried again doing these steps:

 

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

 

But I seem to get errors:

 

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal 

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but
not m4_defun'd

acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but not
m4_defun'd

acinclude.m4:2506: GMP_ASM_X86_MCOUNT is expanded from...

configure.ac:2841: the top level

configure.ac:2841: 

Re: R: R: R: Mpir Installation

[Ron Economos]

sudo apt-get install yasm

Ron

On 4/28/20 05:03, Vincenzo Mone wrote:


Yes Ron,

it waorked since i gave the ./configure command.

I got another error:

checking build system type... x86_64-unknown-linux-gnu

checking host system type... x86_64-unknown-linux-gnu

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... no

checking for mawk... mawk

checking whether make sets $(MAKE)... yes

checking whether make supports nested variables... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking ABI=64

checking compiler gcc -m64 ... yes

checking compiler gcc -m64  -O2... yes

checking compiler gcc -m64 -O2  -march=k8... yes

checking compiler gcc -m64 -O2 -march=k8  -mtune=k8... yes

checking for gcc... gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables...

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking whether gcc understands -c and -o together... yes

checking how to run the C preprocessor... gcc -E

checking for grep that handles long lines and -e... /bin/grep

checking for egrep... /bin/grep -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking minix/config.h usability... no

checking minix/config.h presence... no

checking for minix/config.h... no

checking whether it is safe to define __EXTENSIONS__... yes

checking for gcc... (cached) gcc

checking whether we are using the GNU C compiler... (cached) yes

checking whether gcc accepts -g... (cached) yes

checking for gcc option to accept ISO C89... (cached) none needed

checking whether gcc understands -c and -o together... (cached) yes

checking for gcc option to accept ISO C99... none needed

checking for gcc option to accept ISO Standard C... (cached) none needed

checking how to run the C preprocessor... gcc -E

checking build system compiler gcc... yes

checking for build system preprocessor... gcc -E

checking for build system executable suffix...

checking whether build system compiler is ANSI... yes

checking for build system compiler math library... -lm

Looking for a system-wide yasm...

configure: error: no system-wide yasm found

What am I still missing please?

Thanks

73 de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




*

** GSM  +39 328 7110193  **

  * SMS  +39 328 7110193 *

  *

*Da:*Discuss-gnuradio 
 *Per conto di *Ron 
Economos

*Inviato:* martedì 28 aprile 2020 13:00
*A:* discuss-gnuradio@gnu.org
*Oggetto:* Re: R: R: Mpir Installation

Looks like you're missing M4. Try:

sudo apt-get install autotools-dev automake autoconf

For reference, here's what I'm seeing.

ubuntu@arm:~/xfer/mpir$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize
libtoolize: putting auxiliary files in '.'.
libtoolize: linking file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --no-force
configure.ac:1719: installing './compile'
configure.ac:57: installing './config.guess'
configure.ac:57: installing './config.sub'
configure.ac:67: installing './install-sh'
configure.ac:67: installing './missing'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `.'

Ron

On 4/28/20 03:35, Vincenzo Mone wrote:

Ron,

please this morning I have retried again doing these steps:

git clone git://github.com/wbhart/mpir.git mpir

cd mpir

./autogen.sh

But I seem to get errors:

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal

configure.ac:2838: warning: AC_LIBTOOL_PROG_COMPILER_PIC is
m4_require'd but not m4_defun'd

acinclude.m4:2192: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...

configure.ac:2838: the top level

configure.ac:2841: warning: AC_ENABLE_SHARED is m4_require'd but
not m4_defun'd