hi gem folks,
i just updated my cvs gem and recompiled in the vain hope that single buffer would work on my debian based system, alas..
error: GEM: Unable to create single buffer window
error: GEM: Error creating const context
has anyone worked out a fix or workaround for this one, or even know where the problem lies?
(btw.. pix_kaleidoscope caused unresolved errors and had to be removed from the build process)
..
i just grabbed the latest dyne:bolic disk to find that their build of gem0.87 works without such errors.. but rebooting to dyne: seems a little futile for single buffer rendering..
cheers, dmotd.
On Tuesday, October 14, 2003, at 09:31 AM, dmotd wrote:
hi gem folks,
hi
(btw.. pix_kaleidoscope caused unresolved errors and had to be removed from the build process)
...what compiler are you using? I'm really puzzled by people having problems with pix_kaleidoscope, cuz it worx fine on osx under gcc 3.1, and only certain people on certain linux distros seem to have trouble...
l8r, jamie
i can confirm that gcc 3.3 has problems with that object. the fix is to remove the static from the g_pConstantCosTable declaration. of course then the object will crash but there's probably a fix for that.
cgc
On Tuesday, October 14, 2003, at 09:31 AM, dmotd wrote:
hi gem folks,
hi
(btw.. pix_kaleidoscope caused unresolved errors and had to be removed from the build process)
...what compiler are you using? I'm really puzzled by people having problems with pix_kaleidoscope, cuz it worx fine on osx under gcc 3.1, and only certain people on certain linux distros seem to have trouble...
l8r, jamie
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Wed, 15 Oct 2003, chris clepper wrote:
i can confirm that gcc 3.3 has problems with that object. the fix is
it doesn't on linux (i'm quite sure about this) however gcc<3.0 (2.95) is having problems, as is windows vc6 i have already ifdef'ed the "static" keyword with "NO_HACK" (because it is labeled "pete's hack" which allows at least compilation
anyhow, i don't really understand how the g_pConstantCosTable is meant to work.
to remove the static from the g_pConstantCosTable declaration. of course then the object will crash but there's probably a fix for that.
mfg.a.rd IOhannes
-
chris clepper -
dmotd -
Johannes M Zmoelnig -
tigital