Re: R: R: R: R: R: Mpir Installation
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
R: R: R: R: R: Mpir Installation
nfo 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. You might want to install the Texinfo package: <http://www.gnu.org/software/texinfo/> 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: <http://www.gnu.org/software/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 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 16:00 A: discuss-gnuradio@gnu.org Oggetto: Re: R: R: R: R: Mpir Installation 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&
Re: R: R: R: R: Mpir Installation
dir $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. You might want to install the Texinfo package: <http://www.gnu.org/software/texinfo/> 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: <http://www.gnu.org/software/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 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 14:07 *A:* discuss-gnuradio@gnu.org *Oggetto:* Re: R: R: R: Mpir Installation 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 compi
R: R: R: R: Mpir Installation
.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. You might want to install the Texinfo package: <http://www.gnu.org/software/texinfo/> 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: <http://www.gnu.org/software/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 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 14:07 A: discuss-gnuradio@gnu.org Oggetto: Re: R: R: R: Mpir Installation 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
Re: R: R: R: Mpir Installation
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
R: R: R: Mpir Installation
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:
R: R: R: R: Mpir Installation
Marcus, seems i have done. I have opened GEDIT and pasted 1 line at time. Now I see it like this: 1 SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56" MODE:="0666" SUBSYSTEMS=="usb" 2 ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31" MODE:="0666" 3 KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="fb56", MODE="0666" 4 KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="fb31", MODE="0666" I mean it has added the progressive number on each line. Please you did not told me when I save it which name to give at the file. 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: Marcus Müller > Inviato: lunedì 27 aprile 2020 19:16 > A: Vincenzo Mone > Cc: Gnuradio Mailing List > Oggetto: Re: R: R: R: Mpir Installation > > No command. You need to make a text file, just as I wrote... I give up. > > Best regards, > Marcus > > On 27/04/2020 19.12, Vincenzo Mone wrote: > > OK Marcus, > > I am adding when I reply the Maling list in the CC field. Hope it is > > correct. > > Please which is the correct command to make the UDEV Rules? > > 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: Marcus Müller > >> Inviato: lunedì 27 aprile 2020 19:03 > >> A: Vincenzo Mone > >> Cc: Gnuradio Mailing List > >> Oggetto: Re: R: R: Mpir Installation > >> > >> Vincenzo, > >> > >> On 27/04/2020 18.54, Vincenzo Mone wrote: > >>> Marcus, > >>> apologise I have asked you also in a previous message: Please how to do > to > >> reply via the mailing list? > >>> I am using just the reply button and I understood it is wrong. > >>> Please point me to the right way. > >> > >> I literally did in my last email. > >> > >>> Coming back to the gnuradio OK I am using the 3.8 but if you see on the > >> mailing list, I have > >>> Put several messages as I still cannot getting work the FCDPRPLUS. > >>> I can read from the FCDPROPLUS Readme this and maybe it does not > work: > >> > >>> > >>> Don't forget the udev rules: For instance: > >> > >> You'll find these udev rules have nothing to do with GNU Radio 3.7 or 3.8. > >> > >>> Please can you tell me what to do? > >> > >> A udev rule is a text file that tells your operating system what to do > >> when a new device appears, e.g. when a new USB device gets connected. > >> > >> You need to make a file in /etc/udev/rules.d/ , e.g. > >> /etc/udev/rules.d/fcdproplus.rules, and it needs to contain the four lines > >> > >> SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" > ATTRS{idProduct}=="fb56" > >> MODE:="0666" > >> SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" > ATTRS{idProduct}=="fb31" > >> MODE:="0666" > >> > >> 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" > >> > >> after you've made that file, reboot. That's all. > >> > >> Best regards, > >> Marcus > > > >
R: R: R: Mpir Installation
Marcus, please do not give up. You said me to add the 4 lines but I see 8 lines separated from a LF. What I want to know in the file to make which lines? The first 4 or the second 4 ones? 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: Marcus Müller > Inviato: lunedì 27 aprile 2020 19:03 > A: Vincenzo Mone > Cc: Gnuradio Mailing List > Oggetto: Re: R: R: Mpir Installation > > Vincenzo, > > On 27/04/2020 18.54, Vincenzo Mone wrote: > > Marcus, > > apologise I have asked you also in a previous message: Please how to do to > reply via the mailing list? > > I am using just the reply button and I understood it is wrong. > > Please point me to the right way. > > I literally did in my last email. > > > Coming back to the gnuradio OK I am using the 3.8 but if you see on the > mailing list, I have > > Put several messages as I still cannot getting work the FCDPRPLUS. > > I can read from the FCDPROPLUS Readme this and maybe it does not work: > > > > > Don't forget the udev rules: For instance: > > You'll find these udev rules have nothing to do with GNU Radio 3.7 or 3.8. > > > Please can you tell me what to do? > > A udev rule is a text file that tells your operating system what to do > when a new device appears, e.g. when a new USB device gets connected. > > You need to make a file in /etc/udev/rules.d/ , e.g. > /etc/udev/rules.d/fcdproplus.rules, and it needs to contain the four lines > > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56" > MODE:="0666" > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31" > MODE:="0666" > > 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" > > after you've made that file, reboot. That's all. > > Best regards, > Marcus
Re: R: R: R: Mpir Installation
No command. You need to make a text file, just as I wrote... I give up. Best regards, Marcus On 27/04/2020 19.12, Vincenzo Mone wrote: OK Marcus, I am adding when I reply the Maling list in the CC field. Hope it is correct. Please which is the correct command to make the UDEV Rules? 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: Marcus Müller Inviato: lunedì 27 aprile 2020 19:03 A: Vincenzo Mone Cc: Gnuradio Mailing List Oggetto: Re: R: R: Mpir Installation Vincenzo, On 27/04/2020 18.54, Vincenzo Mone wrote: Marcus, apologise I have asked you also in a previous message: Please how to do to reply via the mailing list? I am using just the reply button and I understood it is wrong. Please point me to the right way. I literally did in my last email. Coming back to the gnuradio OK I am using the 3.8 but if you see on the mailing list, I have Put several messages as I still cannot getting work the FCDPRPLUS. I can read from the FCDPROPLUS Readme this and maybe it does not work: Don't forget the udev rules: For instance: You'll find these udev rules have nothing to do with GNU Radio 3.7 or 3.8. Please can you tell me what to do? A udev rule is a text file that tells your operating system what to do when a new device appears, e.g. when a new USB device gets connected. You need to make a file in /etc/udev/rules.d/ , e.g. /etc/udev/rules.d/fcdproplus.rules, and it needs to contain the four lines SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56" MODE:="0666" SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31" MODE:="0666" 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" after you've made that file, reboot. That's all. Best regards, Marcus smime.p7s Description: S/MIME Cryptographic Signature
R: R: R: Mpir Installation
OK Marcus, I am adding when I reply the Maling list in the CC field. Hope it is correct. Please which is the correct command to make the UDEV Rules? 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: Marcus Müller > Inviato: lunedì 27 aprile 2020 19:03 > A: Vincenzo Mone > Cc: Gnuradio Mailing List > Oggetto: Re: R: R: Mpir Installation > > Vincenzo, > > On 27/04/2020 18.54, Vincenzo Mone wrote: > > Marcus, > > apologise I have asked you also in a previous message: Please how to do to > reply via the mailing list? > > I am using just the reply button and I understood it is wrong. > > Please point me to the right way. > > I literally did in my last email. > > > Coming back to the gnuradio OK I am using the 3.8 but if you see on the > mailing list, I have > > Put several messages as I still cannot getting work the FCDPRPLUS. > > I can read from the FCDPROPLUS Readme this and maybe it does not work: > > > > > Don't forget the udev rules: For instance: > > You'll find these udev rules have nothing to do with GNU Radio 3.7 or 3.8. > > > Please can you tell me what to do? > > A udev rule is a text file that tells your operating system what to do > when a new device appears, e.g. when a new USB device gets connected. > > You need to make a file in /etc/udev/rules.d/ , e.g. > /etc/udev/rules.d/fcdproplus.rules, and it needs to contain the four lines > > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56" > MODE:="0666" > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31" > MODE:="0666" > > 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" > > after you've made that file, reboot. That's all. > > Best regards, > Marcus