I'm trying to install alize and LIA_RAL on ubuntu. I did a checkout of the latest code with subversion from http://alize.univ-avignon.fr/svn/ALIZE/trunk/ and http://alize.univ-avignon.fr/svn/LIA_RAL/trunk/. I've followed the instructions from README file. Alize library has been well installed but during the installation of LIA_RAL i have errors in the command « make »
../../../LIA_SpkTools/include/liatools.h:55:17: erreur fatale: Dense : Aucun fichier ou dossier de ce type
compilation terminée.
make[3]: *** [AcousticSegmentation-AcousticSegmentation.o] Erreur 1
make[3]: quittant le répertoire « /home/ibtissem/lia_ral/LIA_SpkSeg/AcousticSegmentation/src »
make[2]: *** [all-recursive] Erreur 1
make[2]: quittant le répertoire « /home/ibtissem/lia_ral/LIA_SpkSeg/AcousticSegmentation »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/ibtissem/lia_ral/LIA_SpkSeg »
make: *** [all-recursive] Erreur 1
what must i do ? have you any idea ?
Thank you for helping
../../../LIA_SpkTools/include/liatools.h:55:17: erreur fatale: Dense : Aucun fichier ou dossier de ce type compilation terminée.
If you translate this error and try to understand it, it says that the required file is missing. The file could be missing just because file is not there. The compilation can not continue without the file.
To figure out which file is missing and why is it missing you need to look on the lines in the log right above the one you posted. The file search path is specified by the -I options of preprocessor in command line of the compiler. You need to analyze compiler command line just few lines above in the log to understand what happens.
Once you see that -I is not properly specified you can fix that in Makefile.am. Change the line to the following:
AcousticSegmentation_CPPFLAGS=-I../include -I$(top_srcdir)/include/Eigen -I$(top_srcdir)/LIA_SpkTools/include -I$(ALIZE_PATH)/include
The added part is -I$(top_srcdir)/include/Eigen. Then rerun automake to recreate code again.
You will have to do that in several other places.
Overall it's just a bug in software build system. Someone from the authors broke the software recently, you probably want to write a report to the authors about this bug.
Related
During the build of pyodide using the using make method described in the documentation. I am coming across the following error during the emsdk step. Please direct me towards a solution for building the core packages in pyodide PYODIDE_PACKAGES='core'
Error:
Unpacking '/media/savakarrohan/Projects/pyodide/emsdk/emsdk/zips/node-v14.18.2-linux-x64.tar.xz' to '/media/savakarrohan/Projects/pyodide/emsdk/emsdk/node/14.18.2_64bit'
Done installing tool 'node-14.18.2-64bit'.
Installing tool 'releases-upstream-49d45744895c7d7e28acd94a385d7ee361653b4a-64bit'..
Error: Downloading URL 'https://storage.googleapis.com/webassembly/emscripten-releases-builds/linux/49d45744895c7d7e28acd94a385d7ee361653b4a/wasm-binaries.tbz2': <urlopen error [Errno -3] Temporary failure in name resolution>
error: installation failed!
make[1]: *** [Makefile:9: emsdk/.complete] Error 1
make[1]: Leaving directory '/media/savakarrohan/Projects/pyodide/emsdk'
make: *** [Makefile:188: emsdk/emsdk/.complete] Error 2
I am using QT LimeReport on my UBUNTU 18.04 system although i wanted to use it on RPI4.
But i couldn't find any documentation for it and i tried cloning LimeReport from github but it gives error when i use "make".
The error i get is related to
Project ERROR: Unknown module(s) in QT: designercomponents-private
make[1]: *** [Makefile:818: Makefile] Error 3
make[1]: Leaving directory '/home/pi/Desktop/LimeReport/limereport'
make: *** [Makefile:93: sub-limereport-make_first-ordered] Error 2
Has anyone successfully installed and used LimeReport using QT c++ on RPI4.
Install the qttools5-private-dev package to get the missing designercomponents-private QMake file.
I followed instruction by Michael Huang.
My error message reads:
In file included from /home/evadro/quadevac_sim_ws/catkin_ws/src/menge_gazebo/menge_congregate/include/MengeCong.h:10:0,
from /home/evadro/quadevac_sim_ws/catkin_ws/src/menge_gazebo/menge_congregate/src/MengeCong.cpp:8:
/home/evadro/quadevac_sim_ws/catkin_ws/src/menge_gazebo/menge_congregate/../menge_common/include/MengePlugin.h:13:44: fatal error: gazebo/physics/InstancedActor.hh: No such file or directory
compilation terminated.
menge_gazebo/menge_congregate/CMakeFiles/menge_congregate.dir/build.make:62: recipe for target 'menge_gazebo/menge_congregate/CMakeFiles/menge_congregate.dir/src/MengeCong.cpp.o' failed
make[2]: * [menge_gazebo/menge_congregate/CMakeFiles/menge_congregate.dir/src/MengeCong.cpp.o] Error 1
CMakeFiles/Makefile2:4099: recipe for target 'menge_gazebo/menge_congregate/CMakeFiles/menge_congregate.dir/all' failed
make[1]: * [menge_gazebo/menge_congregate/CMakeFiles/menge_congregate.dir/all]
The 2nd error is:
make[1]: *** Waiting for unfinished jobs....
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j24 -l24" failed
Your Error is gazebo/physics/InstancedActor.hh No such file or directory.
this header is not on standard version of Gazebo.
Make Sure you Compiled Gazebo Repo mentioned in External Depenencies Here with No errors. Then Double checks paths so compiler can find the missing headers.
I am trying to install redis-2.6.16 on windows using cygwin. I am getting below error.
Appreciate any help. Thanks.
/c/cygwin64/bin/cc: /c/cygwin64/bin/cc: cannot execute binary file
make[3]: *** [net.o] Error 126
make[3]: Leaving directory `/c/cygwin64/home/redis-2.6.16/deps/hiredis'
make[2]: *** [hiredis] Error 2
make[2]: Leaving directory `/c/cygwin64/home/redis-2.6.16/deps'
make[1]: [persist-settings] Error 2 (ignored)
CC adlist.o
/c/cygwin64/bin/cc: /c/cygwin64/bin/cc: cannot execute binary file
make[1]: *** [adlist.o] Error 126
make[1]: Leaving directory `/c/cygwin64/home/redis-2.6.16/src'
make: *** [all] Error 2
You can't use basic Redis on Windows, you have to use the binaries given by the unsupported port on Windows: https://github.com/MSOpenTech/redis
Basically, you can't just compile the C code of Redis on Windows. And this port has some drawbacks (as Windows does not support fork command), there are "stop the world" operations in it (that redis does not have in its official version): you can't use it for production.
That said, the stack says that cc is missing, you need a C compiler on cygwin, but that won't be enough to make redis work on Windows. Check the last link (github) and download the binaries if you do need to make redis work on Windows.
I modified a few lines of C# code in the source of Mono, and now it does not build anymore:
make[7]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs/mcs'
make[7]: Entering directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs/docs'
/usr/bin/make all-local
make[8]: Entering directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs/docs'
MDOC [net_4_0] cs-errors.tree
mdoc: There is an error in XML document.
See `mdoc help' for more information.
make[8]: *** [cs-errors.tree] Error 1
make[8]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs/docs'
make[7]: *** [do-all] Error 2
make[7]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs/docs'
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs'
make[5]: *** [profile-do--net_4_0--all] Error 2
make[5]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs'
make[4]: *** [profiles-do--all] Error 2
make[4]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/mcs'
make[3]: *** [all-local] Error 2
make[3]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1/runtime'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/nico/src/mono-roman/mono-2.10.8.1'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Build command 'cd mono-2.10.8.1 && dpkg-buildpackage -b -uc' failed.
E: Child process failed
The problem is mdoc: There is an error in XML document. MDOC is a kind of Javadoc for Mono. I am surprised that changing a few benign C# lines would make MDOC fail?
Any tip on what is going on here? I also have no idea what XML document this is about.
The initial analysis I posted in the comments seems to be right. MDOC is loading the cs-errors.config, and using the newly built runtime. The changes you have made produce the following exception while loading said file:
System.InvalidOperationException: Element 'FilesPath' has wrong order in sequence (expected - -1, actual - 0
This was added by your patch. I am guessing you might want to check readBySoapOrder as well, such as:
if (readBySoapOrder && info.ExplicitOrder != ind)
throw new InvalidOperationException(string.Format("Element '{0}' has wrong order in sequence (expected - {1}, actual - {2}", Reader.LocalName, info.ExplicitOrder, ind));
With this little change MDOC is happy and compilation succeeds, but I have no idea if it is the correct behavior.
Try "make clean" before trying "make" again.