freetype_versioncheck failed to compile

[Kelly O'Hair]

The change sounds reasonable, but it's a change to something I have always hated, so it's somewhat distasteful to me
because of that. Having the makefiles build and run an application as part of a sanity check just seems so... 
what is the word....  silly?  :^(

I had hoped that we could just have the sanity check inspect the freetype headers and libraries to
insure the right version, not have to build an application just so we could run it to get the version number.
On the other hand, building this little app is a way to verify that the freetype library links ok.

So to the question of whether this change is ok, basically yes,  but why was this line added:

  53     CC_PROGRAM_OUTPUT_FLAG= -o 

???

-kto


On Jan 4, 2012, at 12:17 AM, Jonathan Lu wrote:

> Anybody interested in this change? does it sound reasonable?
> Thanks and regards!
> 
> On 12/20/2011 08:39 PM, Jonathan Lu wrote:
>> Hi build-dev,
>> 
>> On some Unix environments, such as AIX, the link option to set library search patch is the same as Solaris. But in current script the  option to link tool freetype_versioncheck is the same as Linux, this makes the tool cannot be compiled on AIX.
>> So in order to improve portability, here I propose a patch to adjust the default link option to Solaris' definition.
>> 
>> http://cr.openjdk.java.net/~luchsh/ft_ld_option_sequence/
>> 
>> For other platforms, such as Mac OS X and BSD, I found there's some definitions there in macosx port project[1], so maybe we can just wait for the incoming merge, right?
>> 
>> [1] http://hg.openjdk.java.net/macosx-port/macosx-port/jdk/file/2a76fda3fe23/make/tools/freetypecheck/Makefile
>> 
>> Cheers,
>> - Jonathan Lu
>> 
>