On Nov 24, 2009, at 9:26 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
I got the 10.4/i386 build server going, and I see this:
g++ -c -I/sw/include -I/sw/include/freetype2 -I..
-I/usr/include/FTGL -I/usr/include/freetype2
-I/Users/pd/auto-build/pd-devel/pd/src -DHAVE_CONFIG_H -I/sw/include
-I/sw/include/FTGL -g -O2 -fPIC -freg-struct-return -Os -falign-
loops=32
-falign-functions=32 -falign-jumps=32 -funroll-loops -ffast-math -
mmmx
-fpascal-strings GemPBuffer.cpp -o
../Objects/GemPBuffer.oGemPBuffer.cpp: In constructor
'PBuffer::PBuffer(int, int, int)':
GemPBuffer.cpp:269: error: invalid conversion from 'GLint*' to
'long int*'
GemPBuffer.cpp:269: error: initializing argument 2 of 'CGLError
CGLGetVirtualScreen(_CGLContextObject*, long int*)'GemPBuffer.cpp:
271:
error: invalid conversion from 'GLint*' to 'long int*'
GemPBuffer.cpp:271: error: initializing argument 3 of 'CGLError
CGLChoosePixelFormat(const CGLPixelFormatAttribute*,
_CGLPixelFormatObject**, long int*)'
GemPBuffer.cpp:282: error: invalid conversion from 'GLint*' to
'long int*'
GemPBuffer.cpp:282: error: initializing argument 2 of 'CGLError
CGLGetVirtualScreen(_CGLContextObject*, long int*)'
GemPBuffer.cpp: In member function 'void PBuffer::enable()':
GemPBuffer.cpp:306: error: invalid conversion from 'GLint*' to
'long int*'
GemPBuffer.cpp:306: error: initializing argument 2 of 'CGLError
CGLGetVirtualScreen(_CGLContextObject*, long int*)'
If you need to test which version of gcc is in use,
no, the problem is not the compiler.
it's the headers that are used.
according to the documentation of CGL and according to the header-
files
(on a 10.5 machine), the definition of the function is:
"CGLGetVirtualScreen(CGLContextObj ctx, GLint *screen)"
and not "long int*"
(quoting my other email from beginning of november).
the header file
(/System/Library/Frameworks/OpenGL.framework/Headers/OpenGL.h) on the
build-machine has:
extern CGLError CGLGetVirtualScreen(CGLContextObj ctx, long *screen);
i _strongly_ believe that you have installed the wrong headers.
if you could show me _any_ "official" ressource that uses "long" i
might
be convinced.
in the meantime i have added some hackz to the Gem code that should
make
it compile again.
the svn client installed on the build-machine (/sw/bin/svn) is
somewhat
outdated (1.4.4) and refuses to "svn update" the sandbox.
I definitely did not change the headers, and since they are in /System/
Library, that means no package installs, that's only for stuff that
comes from Apple. Whether they are 'wrong' or not is then a question
for Apple. And we mostly likely have to deal with a workaround :)
Sounds like Apple fixed this in 10.5...
and that's where the compiler text comes in. If you are building on
10.4, you'll be bulding with an older version of gcc. 10.5 has a
newer version. The easiest way to test that is to test for that
build number that I quoted you before.
.hc
----------------------------------------------------------------------------
"[T]he greatest purveyor of violence in the world today [is] my own
government." - Martin Luther King, Jr.
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev
