Here's the answer, I think.  I don't currently have access to a  
Leopard machine, so feel free to beat me to fixing this.  :)

>
>> Leopard use the unix def
>> i change FTVectoriser.cpp like this
>>
>> #ifdef __APPLE_CC__
>>     typedef GLvoid (*GLUTesselatorFunction)();
>> #elif defined( __mips ) || defined( __linux__ ) || defined 
>> ( __FreeBSD__
>> ) || defined( __OpenBSD__ ) || defined( __sun ) || defined  
>> (__CYGWIN__)
>>     typedef GLvoid (*GLUTesselatorFunction)();
>>
>
>
> so what exactly is the difference between apple and the rest of  
> unix here?
> wouldn't it be easier to just add "|| defined (__APPLE__)"


.hc

On Dec 18, 2007, at 2:24 PM, Peter Sachs Collopy wrote:

> I tried to install the package ftgl-2.1.2-3 from the unstable  
> branch on Mac OS 10.5 with fink 0.27.9. It failed, so I ran "fink  
> selfupdate" and tried again, and it failed again, with gcc  
> returning ten errors. The errors are actually just the same two  
> repeated for each of five lines (186-190), and the first pair looks  
> like this:
> /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:186:  
> error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()'
> /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:186:  
> error:   initializing argument 3 of 'void gluTessCallback 
> (GLUtesselator*, GLenum, GLvoid (*)())'
>
> Does anyone have any advice on successfully installing ftgl on my  
> MacBook?
>
> Peter



------------------------------------------------------------------------ 
----

If you are not part of the solution, you are part of the problem.



-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to