Excuse me, I am a MSC computer science student of "The University of Essex". I am doing my dissertation which is around two months long and my topic is "Biped Walking Simulation Using Genetic Programming" which use a software called "SIGEL" to teach virtual robots to walk in a physical 3D-simulation by the method of "Genetic Programming" to evolve control programs. Therefore, my focus is to apply and improve genetic programming to implement and achieve bipedal robot walking application but not to write or implement genetic programming, robot model morphology and simulator from scratch.

I use this software for my small dissertation. Here is the link.
SourceForge.net: Sigel
You can download 1.3 and 1.0 version here.

*PG 368 - SIGEL*
you can download the default experiments, robot models and 1.0 version here.

However, I cannot compile, activate and use this software because of a lot of library errors in my platform. I extract the compressed files, kdesigelSources.1.3.tar.gz and supportingLibs.tar.gz on the "/root/Desktop/". Then, there are a "kdesigel" folder and a "supportingLibs" folder. Then, I would move the "supportingLibs" folder to "/root/Desktop/kdesigel/kdesigel" because there is a same folder "supportingLibs" inside "/root/Desktop/kdesigel/kdesigel". Then, I would go back to "/root/Desktop/kdesigel/" and use this command order, "aclocal", "autoconf", "automake", "./configure" and "make" to start compile and it would compile the files in "supportingLibs" one by one but I face a lot of problems there. My platform should be Fedora Core 4 as well.





This is the record of entering the following commands
"aclocal" -> "autoconf" -> "automake" -> "./configure"



root@eses50 kdesigel # aclocal
root@eses50 kdesigel # autoconf
root@eses50 kdesigel # automake
kdesigel/Makefile.am:43: `LDFLAGS' is a user variable, you should not override it;
kdesigel/Makefile.am:43: use `AM_LDFLAGS' instead.
root@eses50 kdesigel # ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
configure: creating ./config.status
config.status: creating Makefile
config.status: creating kdesigel/Makefile
config.status: creating kdesigel/include/SIGEL_CommonGUI/Makefile
config.status: creating kdesigel/include/Makefile
config.status: creating kdesigel/include/SIGEL_Environment/Makefile
config.status: creating kdesigel/include/SIGEL_GP/Makefile
config.status: creating kdesigel/include/SIGEL_MasterGUI/Makefile
config.status: creating kdesigel/include/SIGEL_Program/Makefile
config.status: creating kdesigel/include/SIGEL_RealInterface/Makefile
config.status: creating kdesigel/include/SIGEL_Robot/Makefile
config.status: creating kdesigel/include/SIGEL_RobotIO/Makefile
config.status: creating kdesigel/include/SIGEL_Simulation/Makefile
config.status: creating kdesigel/include/SIGEL_SlaveGUI/Makefile
config.status: creating kdesigel/include/SIGEL_Tools/Makefile
config.status: creating kdesigel/include/SIGEL_Visualisation/Makefile
config.status: creating kdesigel/src/SIGEL_CommonGUI/Makefile
config.status: creating kdesigel/src/Makefile
config.status: creating kdesigel/src/SIGEL_Environment/Makefile
config.status: creating kdesigel/src/SIGEL_GP/Makefile
config.status: creating kdesigel/src/SIGEL_MasterGUI/Makefile
config.status: creating kdesigel/src/SIGEL_Program/Makefile
config.status: creating kdesigel/src/SIGEL_RealInterface/Makefile
config.status: creating kdesigel/src/SIGEL_Robot/Makefile
config.status: creating kdesigel/src/SIGEL_RobotIO/Makefile
config.status: creating kdesigel/src/SIGEL_Simulation/Makefile
config.status: creating kdesigel/src/SIGEL_SlaveGUI/Makefile
config.status: creating kdesigel/src/SIGEL_Tools/Makefile
config.status: creating kdesigel/src/SIGEL_Visualisation/Makefile
config.status: creating kdesigel/ui/SIGEL_CommonUI/Makefile
config.status: creating kdesigel/ui/Makefile
config.status: creating kdesigel/doc/Makefile
config.status: creating kdesigel/pixmaps/Makefile
config.status: creating kdesigel/templates/Makefile
config.status: creating kdesigel/ui/SIGEL_SlaveUI/Makefile
config.status: creating kdesigel/ui/SIGEL_MasterUI/Makefile
config.status: creating kdesigel/include/MT_Control/Makefile
config.status: creating kdesigel/include/MT_GUI/Makefile
config.status: creating kdesigel/src/MT_Control/Makefile
config.status: creating kdesigel/src/MT_GUI/Makefile
config.status: creating kdesigel/include/MT_GPSystem/Makefile
config.status: creating kdesigel/src/MT_GPSystem/Makefile
config.status: creating kdesigel/ui/MT_UI/Makefile
config.status: executing depfiles commands
root@eses50 kdesigel #






When I enter "make", this is my results and error messages




root@eses50 kdesigel # make
Making all in kdesigel
make[1]: Entering directory `/root/Desktop/kdesigel/kdesigel'
Making all in supportingLibs
make[2]: Entering directory `/root/Desktop/kdesigel/kdesigel/supportingLibs'
cd qhull; \
make;
make[3]: Entering directory `/root/Desktop/kdesigel/kdesigel/supportingLibs/qhull'
gcc -c -O2 -ansi rbox.c
gcc -o rbox rbox.o -O2 -ansi -lm
gcc -c -O2 -ansi unix.c
gcc -c -O2 -ansi user.c
gcc -c -O2 -ansi global.c
gcc -c -O2 -ansi stat.c
gcc -c -O2 -ansi io.c
gcc -c -O2 -ansi geom2.c
gcc -c -O2 -ansi poly2.c
gcc -c -O2 -ansi merge.c
gcc -c -O2 -ansi qhull.c
gcc -c -O2 -ansi geom.c
gcc -c -O2 -ansi poly.c
gcc -c -O2 -ansi qset.c
gcc -c -O2 -ansi mem.c
if ar or ranlib fails, try make qhullx
ar r libqhull.a user.o global.o stat.o io.o geom2.o poly2.o merge.o qhull.o geom.o poly.o qset.o mem.o
ar: creating libqhull.a
the next line may need to be removed.
test -x /bin/ranlib -o -x /usr/bin/ranlib && ranlib libqhull.a
gcc -o qhull -O2 -ansi unix.o -L. -lqhull -lm
chmod +x q_test q_eg q_egtest
./rbox D4 | ./qhull

This is the qhull test case. If any errors or core dumps occur,
recompile qhull with 'make new'. If errors still occur, there is
an incompatibility. You should try a different compiler. You can also
change the choices in user.h. If you discover the source of the problem,
please send mail to qhull_bug@geom.umn.edu.

Type 'qhull' for a short list of options.

Convex hull of 50 points in 4-d:

Number of vertices: 50
Number of facets: 260

Statistics for: ./rbox D4 | ./qhull

Number of points processed: 50
Number of hyperplanes created: 664
Number of distance tests for qhull: 1378
CPU seconds to compute hull (after input): 0

make[3]: Leaving directory `/root/Desktop/kdesigel/kdesigel/supportingLibs/qhull'
cc -fpermissive -O2 -I./newmat09 -c newmat09/bandmat.cpp -o newmat09/bandmat.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/cholesky.cpp -o newmat09/cholesky.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/evalue.cpp -o newmat09/evalue.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/fft.cpp -o newmat09/fft.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/hholder.cpp -o newmat09/hholder.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/jacobi.cpp -o newmat09/jacobi.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/myexcept.cpp -o newmat09/myexcept.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from newmat09/include.h:94,
from newmat09/myexcept.cpp:10:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat1.cpp -o newmat09/newmat1.o;
newmat09/newmat1.cpp: In member function $(B!F (Bchar* NEWMAT::MatrixType::Value() const $(B!G (B:
newmat09/newmat1.cpp:91: warning: invalid conversion from $(B!F (Bconst char* $(B!G (B to $(B!F (Bchar* $(B!G (B
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat2.cpp -o newmat09/newmat2.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat3.cpp -o newmat09/newmat3.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat4.cpp -o newmat09/newmat4.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat5.cpp -o newmat09/newmat5.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat6.cpp -o newmat09/newmat6.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat7.cpp -o newmat09/newmat7.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat8.cpp -o newmat09/newmat8.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmat9.cpp -o newmat09/newmat9.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from newmat09/include.h:94,
from newmat09/newmat9.cpp:8:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
newmat09/newmat9.cpp: In function $(B!F (Bstd::ostream& NEWMAT::operator<<(std::ostream&, const NEWMAT::GeneralMatrix&) $(B!G (B:
newmat09/newmat9.cpp:47: warning: invalid conversion from $(B!F (Blong int $(B!G (B to $(B!F (Bstd::_Ios_Fmtflags $(B!G (B
newmat09/newmat9.cpp:47: warning: initializing argument 1 of $(B!F (Bstd::_Ios_Fmtflags std::ios_base::flags(std::_Ios_Fmtflags) $(B!G (B
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmatex.cpp -o newmat09/newmatex.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from newmat09/include.h:94,
from newmat09/newmatex.cpp:7:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmatnl.cpp -o newmat09/newmatnl.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from newmat09/include.h:94,
from newmat09/newmat.h:8,
from newmat09/newmatap.h:8,
from newmat09/newmatnl.cpp:9:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
cc -fpermissive -O2 -I./newmat09 -c newmat09/newmatrm.cpp -o newmat09/newmatrm.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/sort.cpp -o newmat09/sort.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/solution.cpp -o newmat09/solution.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from newmat09/include.h:94,
from newmat09/solution.cpp:9:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
cc -fpermissive -O2 -I./newmat09 -c newmat09/submat.cpp -o newmat09/submat.o;
cc -fpermissive -O2 -I./newmat09 -c newmat09/svd.cpp -o newmat09/svd.o;
ar r newmat09/libnewmat.a newmat09/bandmat.o newmat09/cholesky.o newmat09/evalue.o newmat09/fft.o newmat09/hholder.o newmat09/jacobi.o newmat09/myexcept.o newmat09/newmat1.o newmat09/newmat2.o newmat09/newmat3.o newmat09/newmat4.o newmat09/newmat5.o newmat09/newmat6.o newmat09/newmat7.o newmat09/newmat8.o newmat09/newmat9.o newmat09/newmatex.o newmat09/newmatnl.o newmat09/newmatrm.o newmat09/sort.o newmat09/solution.o newmat09/submat.o newmat09/svd.o;
ar: creating newmat09/libnewmat.a
cc -fpermissive -O2 -I./cv97 -c cv97/AnchorNode.cpp -o cv97/AnchorNode.o;
In file included from /usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/iostream.h:31,
from cv97/Field.h:16,
from cv97/vrmlfields.h:14,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
In file included from cv97/vrmlfields.h:15,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFBool.h:103:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:16,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFVec2f.h:170:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:17,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFVec3f.h:185:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:18,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFColor.h:146:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:19,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFRotation.h:173:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:20,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFMatrix.h:133:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:21,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFString.h:106:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:23,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFInt32.h:101:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:24,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFFloat.h:101:7: warning: no newline at end of file
In file included from cv97/CLinkedList.h:14,
from cv97/JVector.h:14,
from cv97/MField.h:17,
from cv97/SFImage.h:14,
from cv97/vrmlfields.h:25,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/CLinkedListNode.h:99:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:25,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/SFImage.h:95:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:30,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFVec3f.h:113:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:31,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFColor.h:115:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:32,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFRotation.h:115:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:33,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFInt32.h:110:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:34,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFTime.h:109:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:35,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFFloat.h:108:7: warning: no newline at end of file
In file included from cv97/vrmlfields.h:36,
from cv97/AnchorNode.h:14,
from cv97/AnchorNode.cpp:11:
cv97/MFString.h:111:7: warning: no newline at end of file
cv97/JVector.h: In destructor $(B!F (BJVectorElement<T>::~JVectorElement() $(B!G (B:
/usr/include/stdio.h:154: error: too few arguments to function $(B!F (Bint remove(const char*) $(B!G (B
cv97/JVector.h:29: error: at this point in file
make[2]: *** [cv97/AnchorNode.o] Error 1
make[2]: Leaving directory `/root/Desktop/kdesigel/kdesigel/supportingLibs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Desktop/kdesigel/kdesigel'
make: *** [all-recursive] Error 1
root@eses50 kdesigel #







In fact, I have tried to use the "make" command on "kdevelop3.3" instead of using Terminal when I have entered "aclocal", "autoconf", "automake" and "./configure" in the Terminal. Therefore, "kdevelop3.3" would not stop at the previous error message and it would try to go on compiling. Therefore, I have seen a lot of errors during the compiling of kdevelop3.3.

Besides for binary verison 1.0 and 1.3, I can run it to have a GUI interface but it cannot work properly when I import the default experiments. It would not calculate anything and stop calculation according to the termination condition such as "Generation", "Time by date" or "time by duration".

When using binary version 1.0 to calculate, I would show error messages of "QGVector::operator[]: Index 0 out of range". When using binary version 1.3 to calculate, it would not show any error messages. However, I know that if 1.3 version works, it would show "Computing generation 1, Computing generation 2, ..." something like that but I cannot ensure whether there are such calculation messages for 1.0 version when it works properly.


If you know how to compile and run it properly, Please reply me as soon as possible and your help would be immensely appreciated. If possible, I can include your name and your any messages in my report for my little reward Thank you very much for your attention!!



MSC Computer Science, Artificial Intelligence and Agent Theme
The University of Essex
UK
Wing