I'm trying to compile GEM from the CVS (sys=FedoraFC4; pd.0.90). The GEM.pd-linux object was successfully built but when I try to load the library I get the following message=>
Gem.pd_linux: Gem.pd_linux: undefined symbol: glUseProgramObjectARB Gem: can't load library
Here are the last couple lines of the make command to compile Gem=>
g++ -c -fPIC -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -mmmx -I/usr/X11R6/include -I/usr/include/ffmpeg -I/usr/include/lqt -I/usr/include/lqt -I.. GLdefine.cpp -o GLdefine.o make[1]: Leaving directory `/home/kliger/cvs_20051128/Gem/src/openGL' g++ -o Gem.pd_linux -shared -Wl,-export-dynamic -L/usr/X11R6/lib Base/*.o Controls/*.o Geos/*.o Manips/*.o MarkEx/*.o Nongeos/*.o Particles/*.o Pixes/*.o openGL/*.o -ldv -lavformat -lmpeg3 -ljpeg -ltiff -lGLU -lGL -lXext -lXxf86vm -lXext -lX11 -ldl -lz -lm -L/usr/X11R6/lib -lpthread -L/usr/lib -lquicktime -lpthread -lm -lz -ldl -lquicktime -lpthread -lm -lz -ldl -lMagick++ -lMagick strip --strip-unneeded Gem.pd_linux
Any ideas? Thanks //Brad
Brad Kligerman wrote:
I'm trying to compile GEM from the CVS (sys=FedoraFC4; pd.0.90). The GEM.pd-linux object was successfully built but when I try to load the library I get the following message=>
Gem.pd_linux: Gem.pd_linux: undefined symbol: glUseProgramObjectARB Gem: can't load library
Here are the last couple lines of the make command to compile Gem=>
Any ideas? Thanks //Brad
well, your problem has been introduced by the [glsl_*]-objects, whichare using openGL-2.0 features. your options are: install an openGL that supports openGL-2.0 specs. (if you have an nvidia-card, install the nvidia-glx(-devel) packages; else i don't know (so you are probably out of luck)) OR remove following files from the Gem-sources: src/Manips/glsl_*.{cpp,h,o} src/openGL/GEMglUniform*.{cpp,h,o} and recompile
mfg.asdr. IOhannes
well, your problem has been introduced by the [glsl_*]-objects, whichare using openGL-2.0 features. your options are: install an openGL that supports openGL-2.0 specs. (if you have an nvidia-card, install the nvidia-glx(-devel) packages; else i don't know (so you are probably out of luck)) OR remove following files from the Gem-sources: src/Manips/glsl_*.{cpp,h,o} src/openGL/GEMglUniform*.{cpp,h,o} and recompile
I did what you suggested and recompiled Gem successfully, -lib Gem loads and seems to work fine. Just one last question-- by having removed the above files, what functions in Gem am I sacrificing? Thanks again, /Brad.
On Dec 1, 2005, at 9:36 AM, Brad Kligerman wrote:
remove following files from the Gem-sources: src/Manips/glsl_*.{cpp,h,o} src/openGL/GEMglUniform*.{cpp,h,o} and recompile
I did what you suggested and recompiled Gem successfully, -lib Gem
loads and seems to work fine. Just one last question-- by having
removed the above files, what functions in Gem am I sacrificing?
...you're only "sacrificing" bleeding-edge stuff that isn't quite
ready for primetime yet ;-) Seriously, it should be well known that
compiling Gem from cvs head is going to have some rough edges,
because that's where the focus of development is...in this case,
these objects were only committed last week, and have already gone
thru a few iterations, with a few more likely to go...they work, but
only if you have the hardware and drivers to support
them...conversely, they are extremely undocumented, too...
...besides, they aren't likely to be the place you would start
learning to use Gem anyway...
james
Am 01.12.2005 um 16:30 schrieb james tittle:
...you're only "sacrificing" bleeding-edge stuff that isn't quite
ready for primetime yet ;-) Seriously, it should be well known
that compiling Gem from cvs head is going to have some rough edges,
because that's where the focus of development is...in this case,
these objects were only committed last week, and have already gone
thru a few iterations, with a few more likely to go...they work,
but only if you have the hardware and drivers to support
them...conversely, they are extremely undocumented, too......besides, they aren't likely to be the place you would start
learning to use Gem anyway...
on the other hand the last build is so old that i can understand very
well why somebody would want to get a hand on the CVS version.
On Dec 1, 2005, at 10:54 AM, Max Neupert wrote:
Am 01.12.2005 um 16:30 schrieb james tittle:
...you're only "sacrificing" bleeding-edge stuff that isn't quite
ready for primetime yet ;-) Seriously, it should be well known that
compiling Gem from cvs head is going to have some rough edges,
because that's where the focus of development is...in this case,
these objects were only committed last week, and have already gone
thru a few iterations, with a few more likely to go...they work, but
only if you have the hardware and drivers to support
them...conversely, they are extremely undocumented, too......besides, they aren't likely to be the place you would start
learning to use Gem anyway...on the other hand the last build is so old that i can understand very
well why somebody would want to get a hand on the CVS version.
How about we start putting a stable version of Gem in the pure-data
CVS? Then it'll automatically be built as part of the Pd-extended
build system, and the gem-dev's won't have to worry about making binary
releases anymore, except for test versions, or whatever.
Tell me a tag to use, and I'll even do the import to pure-data CVS.
.hc ________________________________________________________________________ ____
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity."
-John Gilmore
On 12/1/05, james tittle <tigital@mac.com > wrote:
On Dec 1, 2005, at 9:36 AM, Brad Kligerman wrote:
remove following files from the Gem-sources: src/Manips/glsl_*.{cpp,h,o} src/openGL/GEMglUniform*.{cpp,h,o} and recompile
I did what you suggested and recompiled Gem successfully, -lib Gem loads and seems to work fine. Just one last question-- by having removed the above files, what functions in Gem am I sacrificing?
...you're only "sacrificing" bleeding-edge stuff that isn't quite ready for primetime yet ;-) Seriously, it should be well known that compiling Gem from cvs head is going to have some rough edges, because that's where the focus of development is...in this case, these objects were only committed last week, and have already gone thru a few iterations, with a few more likely to go...they work, but only if you have the hardware and drivers to support them...conversely, they are extremely undocumented, too...
...besides, they aren't likely to be the place you would start learning to use Gem anyway...
Thanks for the response... yeah, maybe not a good place to learn, but, I need the CVS especially for the [gemlist_info] object that's helping me measure real (projected) space by tracking screen space object matrices for constructing a rather complex installation. Also, [pix_2gem] apparently likes the CVS better than 0.90 (even though it still will not compile). /Brad.
Brad Kligerman wrote:
I did what you suggested and recompiled Gem successfully, -lib Gem loads and seems to work fine. Just one last question-- by having removed the above files, what functions in Gem am I sacrificing?
you cannot load openGL-2.0 shaders (vertex+fragment shaders) but you are not really sacrificing them, since your driver obviously does not support them anyhow.
mf.asdr IOhannes
-
Brad Kligerman -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
james tittle -
Max Neupert