[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freetype] Compiling 2.1.7 on Mac OS X

From: Garrick Meeker
Subject: Re: [Freetype] Compiling 2.1.7 on Mac OS X
Date: Tue, 23 Mar 2004 11:27:46 -0800
User-agent: KMail/1.6

It looks like configure is setting XX_ANSICFLAGS instead of XX_ANSIFLAGS to 
remove -ansi when this flag is given.  If the inline thing isn't fixed, this 
is an alternative solution.

On Sunday 14 March 2004 02:05, Werner LEMBERG wrote:
> > The error is in the source file ftmac.c, which includes a
> > Mac-specific header using 'inline' keywords by default.  The problem
> > comes from the -ansi switch to gcc, as Garrick Meeker has recently
> > reported, which causes gcc not to recognize 'inline'.
> >
> > The simple solution is to change builds/unix/configure to not use
> > -ansi if $host matches *-apple*.  However it would be a shame to
> > disable -ansi for the whole build; do you know how to tweak the
> > builds/unix makefile so that only ftmac.c is built without -ansi?  I
> > guess it would have to be separated out from ftbase.c in that
> > case...
> Various possibilities come to my mind, to be applied to ftmac.c rather
> than the makefile:
>   . Redefine `OS_INLINE' to be `__inline__'.  This survives even gcc's
>     -ansi switch.
>   . Redefine `OS_INLINE' to be a no-op.
>   . Compile FreeType with g++.  `inline' is a normal keyword then.  [I
>     regularly test whether FreeType really builds with g++.]
>       Werner
> _______________________________________________
> Freetype mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]