freetype-devel
[Top][All Lists]
Advanced

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

Re: [ft-devel] latest freetype compilation issues on Linux


From: mpsuzuki
Subject: Re: [ft-devel] latest freetype compilation issues on Linux
Date: Thu, 15 Jul 2010 16:32:31 +0900

Hi Anil,

I'm sorry for lated response for this issue, still I
cannot reproduce this issue by myself. I could build
freetype-2.3.12 (and 2.4.0 too) successfully by cross
compiler for SGI mips systems.

I guess, the error you got is because your C compiler
included legacy FT2 header files from installed system
(not from source tree), the macros introduced in newer
versions are left as undefined, and caused errors.

But, looking at your config.log and make.log, they look
as if the options passed to your C compiler is normal:
-I/root/freetype-2.3.12/objs, -I./builds/unix, and
-I/root/freetype-2.3.12/include are passed for first.
Yet I cannot understand why appropriate header files
are not included.

Could you build FT2 with gcc option "-save-temps"
(which preserve the preprocessed files) and send me
"ftbase.i"?

Regards,
mpsuzuki





On Mon, 5 Jul 2010 09:36:46 +0530
anil v <address@hidden> wrote:

>Hi mpsuzuki,
>
>    Please find the config.log and make.log which are attached with this
>mail.
>
>Thanks,
>Anil.V
>
>On 5 July 2010 03:01, <address@hidden> wrote:
>
>> On Sun, 4 Jul 2010 22:04:45 +0530
>> anil v <address@hidden> wrote:
>>
>> >Hi mpsuzuki,
>> >   Thanks for your reply. I am following below mentioned configuration
>> >./configure \
>> >        --host="mipsel-linux" \
>> >        --build=i686-linux \
>> >        --prefix=/root/freetype2/bins \
>> >        --enable-shared \
>> >        --disable-static
>> >
>> >with above configuration i am able to compile freetype-2.3.5 successfully.
>>
>> Hmm, it looks good, I want to have more detailed info.
>> Could you send me config.log and the command log when
>> you execute "make"? The command log can be logged by
>> "make 2>&1 | tee make.log" (on Bourne-shell families).
>>
>> Regards,
>> mpsuzuki
>>
>



reply via email to

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