[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft] Freetype2 compilation error
From: |
suzuki toshiya |
Subject: |
Re: [ft] Freetype2 compilation error |
Date: |
Tue, 19 Mar 2013 17:12:34 +0900 |
User-agent: |
Mozilla-Thunderbird 2.0.0.12 (X11/20080406) |
Thank you for prompt checking.
Could you post config.log (generated with testing tarball)?
I want to know ftconfig.in checking finishes with "yes" or
"no".
Regards,
mpsuzuki
HCL Infosystems Ltd wrote:
> Yes now its working. Thanks a lot!!!
>
> Regards
> Amit
>
> ----- Original Message -----
> From: "suzuki toshiya" <address@hidden>
> To: "freetype" <address@hidden>
> Cc: "HCL Infosystems Ltd" <address@hidden>, "Werner LEMBERG" <address@hidden>
> Sent: Tuesday, March 19, 2013 1:19:31 PM
> Subject: Re: [ft] Freetype2 compilation error
>
> Just I've uploaded testing tarball.
>
> http://gyvern.ipc.hiroshima-u.ac.jp/~mpsuzuki/freetype-2.4.11_fix-for-xlc-cpp_20130319a.tar.xz
>
> Please try and see how warning on ftconfig.in checking will
> be changed, or not.
>
> Regards,
> mpsuzuki
>
>
> P.S.
> The difference from genuine 2.4.11 is quite small, like this.
>
> diff --git a/builds/unix/configure.raw b/builds/unix/configure.raw
> index bf26061..634cfc1 100644
> --- a/builds/unix/configure.raw
> +++ b/builds/unix/configure.raw
> @@ -102,13 +102,15 @@ AC_CHECK_SIZEOF([long])
>
> AC_MSG_CHECKING([whether cpp computation of bit length in ftconfig.in works])
> orig_CPPFLAGS="${CPPFLAGS}"
> -CPPFLAGS="-I${srcdir} -I. ${CPPFLAGS}"
> +CPPFLAGS="-I${srcdir} -I. ${CPPFLAGS} -DFT2_CPP_TESTING"
>
> ac_clean_files=
> for f in ft2build.h ftoption.h ftstdlib.h; do
> if test ! -f $f; then
> ac_clean_files="$ac_clean_files $f"
> - touch $f
> + echo '#ifndef FT2_CPP_TESTING' > ${f}
> + echo '# error "autoconf temporal file for CPP testing is included"' >> $f
> + echo '#endif' >> $f
> fi
> done
>
>
> suzuki toshiya wrote:
>> OK, I will make a testing tarball with new configure script.
>> Please wait a while.
>>
>> Regards,
>> mpsuzuki
>>
>> HCL Infosystems Ltd wrote:
>>> Hello mpsuzuki,
>>>
>>> Thanks for your reply!!!
>>> Yes you are correct. I am getting this warning while configuration and for
>>> me it should get resolve first before make and make install.
>>>
>>> Regards
>>> Amit
>>>
>>> ----- Original Message -----
>>> From: "suzuki toshiya" <address@hidden>
>>> To: "HCL Infosystems Ltd" <address@hidden>
>>> Cc: address@hidden
>>> Sent: Tuesday, March 19, 2013 12:23:33 PM
>>> Subject: Re: [ft] Freetype2 compilation error
>>>
>>> Hi,
>>>
>>> Sorry for your inconvenience. Your quotation seems to be the messages
>>> during the configuration, not during compilation. Do you mean that
>>> the irregular warning like
>>>
>>>> checking whether cpp computation of bit length in ftconfig.in works...
>>>> "./ft2build.h", line 1: 1506-229 (W) File is empty.
>>>> "ftoption.h", line 1: 1506-229 (W) File is empty.
>>>> "ftstdlib.h", line 1: 1506-229 (W) File is empty.
>>>> no
>>> should be fixed? Of course it should be cared (and I will do), but if
>>> you have other troubles during the compilation, please post.
>>>
>>> # I guess the background of the warning is the inclusion of the
>>> # empty header files created aslike:
>>> #
>>> # ac_clean_files=
>>> # for f in ft2build.h ftoption.h ftstdlib.h; do
>>> # if test ! -f $f; then
>>> # ac_clean_files="$ac_clean_files $f"
>>> # touch $f
>>> # fi
>>> # done
>>> #
>>> # some more content would be expected to calm /bin/cpp of XLC compiler,
>>> # I guess.
>>>
>>>
>>> Regards,
>>> mpsuzuki
>>>
>>> HCL Infosystems Ltd wrote:
>>>> Dear Team,
>>>>
>>>> I am getting the below error in red while compiling freetype-2.4.11 on AIX
>>>> 5.3.
>>>>
>>>> ##################################################QUOTE##################################################
>>>>
>>>> FreeType build system -- automatic system detection
>>>>
>>>> The following settings are used:
>>>>
>>>> platform unix
>>>> compiler /usr/vac/bin/xlc
>>>> configuration directory ./builds/unix
>>>> configuration rules ./builds/unix/unix.mk
>>>>
>>>> If this does not correspond to your system or settings please remove the
>>>> file
>>>> `config.mk' from this directory then read the INSTALL file for help.
>>>>
>>>> Otherwise, simply type `/gpfs1/home/amit/SOURCE/make-3.82/bin/make' again
>>>> to build the library,
>>>> or `/gpfs1/home/amit/SOURCE/make-3.82/bin/make refdoc' to build the API
>>>> reference (the latter needs python).
>>>>
>>>> Generating modules list in ./objs/ftmodule.h...
>>>> * module: truetype (Windows/Mac font files with extension *.ttf or *.ttc)
>>>> * module: type1 (Postscript font files with extension *.pfa or *.pfb)
>>>> * module: cff (OpenType fonts with extension *.otf)
>>>> * module: cid (Postscript CID-keyed fonts, no known extension)
>>>> * module: pfr (PFR/TrueDoc font files with extension *.pfr)
>>>> * module: type42 (Type 42 font files with no known extension)
>>>> * module: winfnt (Windows bitmap fonts with extension *.fnt or *.fon)
>>>> * module: pcf (pcf bitmap fonts)
>>>> * module: bdf (bdf bitmap fonts)
>>>> * module: sfnt (helper module for TrueType & OpenType formats)
>>>> * module: autofit (automatic hinting module)
>>>> * module: pshinter (Postscript hinter module)
>>>> * module: raster (monochrome bitmap renderer)
>>>> * module: smooth (anti-aliased bitmap renderer)
>>>> * module: smooth (anti-aliased bitmap renderer for LCDs)
>>>> * module: smooth (anti-aliased bitmap renderer for vertical LCDs)
>>>> * module: psaux (Postscript Type 1 & Type 2 helper module)
>>>> * module: psnames (Postscript & Unicode Glyph name handling)
>>>> done.
>>>> cd builds/unix; ./configure '--prefix=/gpfs1/home/amit/freetype-2.4.11'
>>>> checking build system type... powerpc-ibm-aix5.3.0.0
>>>> checking host system type... powerpc-ibm-aix5.3.0.0
>>>> checking for gcc... /usr/vac/bin/xlc
>>>> checking whether the C compiler works... yes
>>>> checking for C compiler default output file name... a.out
>>>> checking for suffix of executables...
>>>> checking whether we are cross compiling... no
>>>> checking for suffix of object files... o
>>>> checking whether we are using the GNU C compiler... no
>>>> checking whether /usr/vac/bin/xlc accepts -g... yes
>>>> checking for /usr/vac/bin/xlc option to accept ISO C89... none needed
>>>> checking how to run the C preprocessor... /bin/cpp
>>>> checking for rmdir... rmdir
>>>> checking for a BSD-compatible install... /opt/freeware/bin/install -c
>>>> checking for grep that handles long lines and -e... /usr/bin/grep
>>>> checking for egrep... /usr/bin/grep -E
>>>> checking for ANSI C header files... yes
>>>> checking for sys/types.h... yes
>>>> checking for sys/stat.h... yes
>>>> checking for stdlib.h... yes
>>>> checking for string.h... yes
>>>> checking for memory.h... yes
>>>> checking for strings.h... yes
>>>> checking for inttypes.h... yes
>>>> checking for stdint.h... yes
>>>> checking for unistd.h... yes
>>>> checking fcntl.h usability... yes
>>>> checking fcntl.h presence... yes
>>>> checking for fcntl.h... yes
>>>> checking for unistd.h... (cached) yes
>>>> checking for an ANSI C-conforming const... yes
>>>> checking size of int... 4
>>>> checking size of long... 8
>>>> checking whether cpp computation of bit length in ftconfig.in works...
>>>> "./ft2build.h", line 1: 1506-229 (W) File is empty.
>>>> "ftoption.h", line 1: 1506-229 (W) File is empty.
>>>> "ftstdlib.h", line 1: 1506-229 (W) File is empty.
>>>> no
>>>> checking for stdlib.h... (cached) yes
>>>> checking for unistd.h... (cached) yes
>>>> checking for sys/param.h... yes
>>>> checking for getpagesize... yes
>>>> checking for working mmap... yes
>>>> checking whether munmap is declared... yes
>>>> checking for munmap's first parameter type... void *
>>>> checking for memcpy... yes
>>>> checking for memmove... yes
>>>> checking for gzsetparams in -lz... yes
>>>> checking zlib.h usability... yes
>>>> checking zlib.h presence... yes
>>>> checking for zlib.h... yes
>>>> checking for BZ2_bzDecompress in -lbz2... yes
>>>> checking bzlib.h usability... yes
>>>> checking bzlib.h presence... yes
>>>> checking for bzlib.h... yes
>>>> checking how to print strings... print -r
>>>> checking for a sed that does not truncate output... /usr/bin/sed
>>>> checking for fgrep... /usr/bin/grep -F
>>>> checking for non-GNU ld... /usr/bin/ld
>>>> checking if the linker (/usr/bin/ld) is GNU ld... no
>>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>>>> checking whether ln -s works... yes
>>>> checking the maximum length of command line arguments... 393216
>>>> checking whether the shell understands some XSI constructs... yes
>>>> checking whether the shell understands "+="... no
>>>> checking how to convert powerpc-ibm-aix5.3.0.0 file names to
>>>> powerpc-ibm-aix5.3.0.0 format... func_convert_file_noop
>>>> checking how to convert powerpc-ibm-aix5.3.0.0 file names to toolchain
>>>> format... func_convert_file_noop
>>>> checking for /usr/bin/ld option to reload object files... -r
>>>> checking for objdump... no
>>>> checking how to recognize dependent libraries... pass_all
>>>> checking for dlltool... no
>>>> checking how to associate runtime and link libraries... print -r --
>>>> checking for archiver @FILE support... no
>>>> checking for strip... strip
>>>> checking for ranlib... ranlib
>>>> checking for gawk... gawk
>>>> checking command to parse /usr/bin/nm -B output from /usr/vac/bin/xlc
>>>> object... ok
>>>> checking for sysroot... no
>>>> checking for mt... mt
>>>> checking if mt is a manifest tool... no
>>>> checking for dlfcn.h... yes
>>>> checking for objdir... .libs
>>>> checking for /usr/vac/bin/xlc option to produce PIC... -DPIC
>>>> checking if /usr/vac/bin/xlc PIC flag -DPIC works... yes
>>>> checking if /usr/vac/bin/xlc static flag -bnso -bI:/lib/syscalls.exp
>>>> works... no
>>>> checking if /usr/vac/bin/xlc supports -c -o file.o... yes
>>>> checking if /usr/vac/bin/xlc supports -c -o file.o... (cached) yes
>>>> checking whether the /usr/vac/bin/xlc linker (/usr/bin/ld) supports shared
>>>> libraries... yes
>>>> checking dynamic linker characteristics... aix5.3.0.0 ld.so
>>>> checking how to hardcode library paths into programs... immediate
>>>> checking whether stripping libraries is possible... no
>>>> checking if libtool supports shared libraries... yes
>>>> checking whether to build shared libraries... yes
>>>> checking whether to build static libraries... no
>>>> configure: creating ./config.status
>>>> config.status: creating unix-cc.mk
>>>> config.status: creating unix-def.mk
>>>> config.status: creating freetype-config
>>>> config.status: creating freetype2.pc
>>>> config.status: creating ftconfig.h
>>>> config.status: executing libtool commands
>>>> gmake: Nothing to be done for `unix'.
>>>> ##################################################UNQUOTE##################################################
>>>>
>>>>
>>>> Please help me to get it resolved.
>>>>
>>>> Regards
>>>> Amit
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Freetype mailing list
>>>> address@hidden
>>>> https://lists.nongnu.org/mailman/listinfo/freetype
>>
>> _______________________________________________
>> Freetype mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/freetype
>
- [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/19
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/19
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/19
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/19
- Re: [ft] Freetype2 compilation error,
suzuki toshiya <=
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/19
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/19
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/19
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/19
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/19
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/19
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/20
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/20
- Re: [ft] Freetype2 compilation error, HCL Infosystems Ltd, 2013/03/20
- Re: [ft] Freetype2 compilation error, suzuki toshiya, 2013/03/20