Hi all. I'm new here. I've been using Max/MSP/softVNS for a few years and have made the switch to Linux for multimedia. I read a glowing review of using GEM and PD for a multimedia installation so I grabbed the source code and gave it a go.
It appears that version 0.87, which is the only version on the website, has some real linking problems. I'm just getting into Linux development, so I'm partially familliar with the magical autoconf system, but this looks like it goes beyond an autoconf thing.
Issues I've encountered:
1) Whoever made the source tarball kept their Makefile in there. Without doing a 'make distclean', ./configure reported a bunch of wrong paths because it was using cached info from whoever made the tarball.
2) I have libmpeg3 installed and the headers are in /usr/include/libmpeg3/libmpeg3.h ./configure does not recognize this.
3) memcpy, a function provided by the string.h standard C library, is not included in some files in the Pixes directory. I included this and things are a little better.
4) The source won't compile on my system. For me it bails out here:
echo ----------../Pixes---------- make[1]: Entering directory `/usr/local/src/gem-0.87/src/Pixes' g++ -c -g -fPIC -I../ -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/gltt -I../../../GemLibs/particle -I../../../GemLibs/liborb -I../../../GemLibs/glm -I/usr/local/include -I.. pix_videoLinux.cpp -o pix_videoLinux.o In file included from ../Pixes/pix_video.h:20, from pix_videoLinux.h:38, from pix_videoLinux.cpp:44: ../Base/GemBase.h:27:8: warning: extra tokens at end of #endif directive pix_videoLinux.cpp:59: default argument given for parameter 1 of ` pix_videoLinux::pix_videoLinux(float = 320, float = 240)' pix_videoLinux.h:68: after previous specification in ` pix_videoLinux::pix_videoLinux(float = 320, float = 240)' pix_videoLinux.cpp:59: default argument given for parameter 2 of ` pix_videoLinux::pix_videoLinux(float = 320, float = 240)' pix_videoLinux.h:68: after previous specification in ` pix_videoLinux::pix_videoLinux(float = 320, float = 240)' make[1]: *** [pix_videoLinux.o] Error 1 make[1]: Leaving directory `/usr/local/src/gem-0.87/src/Pixes' make: *** [subdirs] Error 255
Which is also in the Pixes directory, which seems to be where most of the compilation problems are. I read on the list archives that about a year ago there was an issue with G++ 3.0. It seems these problems are still there. I have version 3.2.1 installed and so far GEM is the only software giving me problems. So what's required to get the source G++ 3.0 compatible?
-l[e^2] ------------------------------ http://www.fallingforward.net/ people experimenting with music, art and technology
at an impoverished guess i would suggest a gcc-2.95 compile. /usr/bin/gcc is usually just a symlink to your actual gcc -v so i would suggest trying 'ln -s /usr/bin/gcc-2.95 /usr/bin/gcc'.
but then again it could be your libmpeg3 headers so edit your configure file or edit your path to include this dir. remember to remove config.cache if it exists. also remember to run ldconfig if you make changes.
someone probably [will] have a better idea.
de/
On Sun, 10 Aug 2003 16:38:34 -0400 (EDT) Lee Azzarello lee@fallingforward.net wrote:
//Hi all. I'm new here. I've been using Max/MSP/softVNS for a few years and //have made the switch to Linux for multimedia. I read a glowing review of //using GEM and PD for a multimedia installation so I grabbed the source //code and gave it a go. // //It appears that version 0.87, which is the only version on the website, //has some real linking problems. I'm just getting into Linux development, //so I'm partially familliar with the magical autoconf system, but this //looks like it goes beyond an autoconf thing. // //Issues I've encountered: // //1) Whoever made the source tarball kept their Makefile in there. Without //doing a 'make distclean', ./configure reported a bunch of wrong paths //because it was using cached info from whoever made the tarball. // //2) I have libmpeg3 installed and the //headers are in /usr/include/libmpeg3/libmpeg3.h //./configure does not recognize this. // //3) memcpy, a function provided by the string.h standard C library, is not //included in some files in the Pixes directory. I included this and things //are a little better. // //4) The source won't compile on my system. For me it bails out here: // // echo ----------../Pixes---------- //make[1]: Entering directory `/usr/local/src/gem-0.87/src/Pixes' //g++ -c -g -fPIC -I../ -I/usr/include/glib-1.2 -I/usr/lib/glib/include //-I/usr/include/gltt -I../../../GemLibs/particle -I../../../GemLibs/liborb //-I../../../GemLibs/glm -I/usr/local/include -I.. pix_videoLinux.cpp -o //pix_videoLinux.o //In file included from ../Pixes/pix_video.h:20, // from pix_videoLinux.h:38, // from pix_videoLinux.cpp:44: //../Base/GemBase.h:27:8: warning: extra tokens at end of #endif directive //pix_videoLinux.cpp:59: default argument given for parameter 1 of ` // pix_videoLinux::pix_videoLinux(float = 320, float = 240)' //pix_videoLinux.h:68: after previous specification in ` // pix_videoLinux::pix_videoLinux(float = 320, float = 240)' //pix_videoLinux.cpp:59: default argument given for parameter 2 of ` // pix_videoLinux::pix_videoLinux(float = 320, float = 240)' //pix_videoLinux.h:68: after previous specification in ` // pix_videoLinux::pix_videoLinux(float = 320, float = 240)' //make[1]: *** [pix_videoLinux.o] Error 1 //make[1]: Leaving directory `/usr/local/src/gem-0.87/src/Pixes' //make: *** [subdirs] Error 255 // //Which is also in the Pixes directory, which seems to be where most of the //compilation problems are. I read on the list archives that about a year //ago there was an issue with G++ 3.0. It seems these problems are still //there. I have version 3.2.1 installed and so far GEM is the only software //giving me problems. So what's required to get the source G++ 3.0 //compatible? // //-l[e^2] //------------------------------ //http://www.fallingforward.net/ //people experimenting with music, art and technology // // //_______________________________________________ //PD-dev mailing list //PD-dev@iem.at //http://iem.at/cgi-bin/mailman/listinfo/pd-dev // //
//-->
nick -> delire home -> http://selectparks.net key -> http://selectparks.net/jkey.txt
at an impoverished guess i would suggest a gcc-2.95 compile. /usr/bin/gcc is usually just a symlink to your actual gcc -v so i would suggest trying 'ln -s /usr/bin/gcc-2.95 /usr/bin/gcc'.
but then again it could be your libmpeg3 headers so edit your configure file or edit your path to include this dir. remember to remove config.cache if it exists. also remember to run ldconfig if you make changes.
someone probably [will] have a better idea.
no i think u mentioned the right points, u have to use gcc-2.95, then it compiles fine (except pix_kaleidoscope from cvs).
e
Zitiere Lee Azzarello lee@fallingforward.net:
.
Issues I've encountered:
- Whoever made the source tarball kept their Makefile in there.
that was me...
indeed, the gem-0.87 source-release has a lot of drawbacks, deficiencies and bugs.
however, i hope we will in near future get a gem-0.888 release with all of the problems fixed
i personally suggest, you should use the CVS-version of Gem (for instructions see http://gem.iem.at/downloads/ (or was it /download/ ?)
all the bugs you have mentioned should be fixed in there.
mfg.as.rd IOhannes
-
delire -
Lee Azzarello -
rat＠telecoma.net -
zmoelnig＠iem.at