Dear Amit, Thanks again! According to the line
> "./cpp-bitshift-test2.c", line 11.32: 1506-207 (W) Integer constant > 0x100000000L out of range. the integer constant greater than 32-bit is inappropriate for xlc's cpp. I think FreeType2 header for xlc should not be shared between 32-bit and 64-bit systems. I will investigate any predefined macros to detect xlc (or the case that the max sizes of the integer constants are different between cpp & C compiler), but the immediate fix for the next release of FreeType2 would disable the bi-arch header file. Regards, mpsuzuki HCL Infosystems Ltd wrote: > Dear mpsuzuki, > > Please find the below o/p: > > ###########################################QUOTE########################################### > #line 234 "/usr/include/float.h" > extern unsigned int SINFINITY; > extern unsigned int _DBLINF[2]; > extern unsigned int SQNAN; > extern unsigned int DQNAN[2]; > extern unsigned int SSNAN; > extern unsigned int DSNAN[2]; > #line 265 > typedef unsigned short fprnd_t; > #line 274 > fprnd_t fp_read_rnd(void); > fprnd_t fp_swap_rnd(fprnd_t rnd); > "./cpp-bitshift-test2.c", line 3.7: 1506-207 (W) Integer constant > 0xFFFFFFFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 3.38: 1506-207 (W) Integer constant > 0x10000000000000000L out of range. > "./cpp-bitshift-test2.c", line 5.9: 1506-207 (W) Integer constant > 0x7FFFFFFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 5.40: 1506-207 (W) Integer constant > 0xFFFFFFFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 7.9: 1506-207 (W) Integer constant > 0xFFFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 7.36: 1506-207 (W) Integer constant > 0x1000000000000L out of range. > "./cpp-bitshift-test2.c", line 9.9: 1506-207 (W) Integer constant > 0x7FFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 9.36: 1506-207 (W) Integer constant > 0xFFFFFFFFFFFFL out of range. > "./cpp-bitshift-test2.c", line 11.32: 1506-207 (W) Integer constant > 0x100000000L out of range. > #line 27 "./cpp-bitshift-test2.c" > The max bitshift by C preprocessor would be 31 > ###########################################UNQUOTE########################################### > > Regards > Amit > > ----- Original Message ----- > From: "suzuki toshiya" <[email protected]> > To: "HCL Infosystems Ltd" <[email protected]> > Cc: "Werner LEMBERG" <[email protected]>, "freetype" <[email protected]> > Sent: Wednesday, March 20, 2013 3:42:08 PM > Subject: Re: [ft] Freetype2 compilation error > > Dear Amit, > > Thanks! It seems that xlc's cpp cannot handle bitshift for > 64-bit constants, at least, if the constants lack the suffix > for long (or unsigned long) integer. I attached yet another > testing code that the constants greater than 32-bit range > have the suffix "L" to indicate long type. Could you execute > /bin/cpp ./cpp-bitshift-test2.c > again? > > Regards, > mpsuzuki > > HCL Infosystems Ltd wrote: >> Dear mpsuzuki, >> >> Please find the below o/p of '/bin/cpp ./cpp-bitshift-test.c' command: >> >> ###########################################QUOTE########################################### >> #line 234 "/usr/include/float.h" >> extern unsigned int SINFINITY; >> extern unsigned int _DBLINF[2]; >> extern unsigned int SQNAN; >> extern unsigned int DQNAN[2]; >> extern unsigned int SSNAN; >> extern unsigned int DSNAN[2]; >> #line 265 >> typedef unsigned short fprnd_t; >> #line 274 >> fprnd_t fp_read_rnd(void); >> fprnd_t fp_swap_rnd(fprnd_t rnd); >> "./cpp-bitshift-test.c", line 3.7: 1506-207 (W) Integer constant >> 0xFFFFFFFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 3.37: 1506-207 (W) Integer constant >> 0x10000000000000000 out of range. >> "./cpp-bitshift-test.c", line 5.9: 1506-207 (W) Integer constant >> 0x7FFFFFFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 5.39: 1506-207 (W) Integer constant >> 0xFFFFFFFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 7.9: 1506-207 (W) Integer constant >> 0xFFFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 7.35: 1506-207 (W) Integer constant >> 0x1000000000000 out of range. >> "./cpp-bitshift-test.c", line 9.9: 1506-207 (W) Integer constant >> 0x7FFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 9.35: 1506-207 (W) Integer constant >> 0xFFFFFFFFFFFF out of range. >> "./cpp-bitshift-test.c", line 11.31: 1506-207 (W) Integer constant >> 0x100000000 out of range. >> #line 27 "./cpp-bitshift-test.c" >> The max bitshift by C preprocessor would be 31 >> ###########################################UNQUOTE########################################### >> >> Regards >> Amit >> >> ----- Original Message ----- >> From: "suzuki toshiya" <[email protected]> >> To: "HCL Infosystems Ltd" <[email protected]> >> Cc: "Werner LEMBERG" <[email protected]>, "freetype" <[email protected]> >> Sent: Wednesday, March 20, 2013 2:38:05 PM >> Subject: Re: [ft] Freetype2 compilation error >> >> Dear Amit, >> >> I attached a small C-like source for /bin/cpp, >> it checks the maximum bitshift operation that >> C preprocessor can work well. Please execute >> >> /bin/cpp ./cpp-bitshift-test.c >> >> and send me its output. >> >> For example, the output by GCC on Linux/i386 >> finishes as: >> ----------------------------------------------- >> [snip] >> # 2 "/dev/shm/cpp-bitshift-test.c" 2 >> /dev/shm/cpp-bitshift-test.c:3:37: warning: integer constant is too large >> for its type [enabled by default] >> # 27 "/dev/shm/cpp-bitshift-test.c" >> The max bitshift by C preprocessor would be 63 >> ----------------------------------------------- >> so we can expect that cpp macro like ((ULONG_MAX >> 63) == 0) >> can be used to check the size of unsigned long. >> >> Regards, >> mpsuzuki >> >> HCL Infosystems Ltd wrote: >>> Dear mpsuzuki, >>> >>> Thanks a lot for below information. >>> >>> Regards >>> Amit >>> >>> ----- Original Message ----- >>> From: "suzuki toshiya" <[email protected]> >>> To: "HCL Infosystems Ltd" <[email protected]> >>> Cc: "Werner LEMBERG" <[email protected]>, "freetype" <[email protected]> >>> Sent: Tuesday, March 19, 2013 6:38:29 PM >>> Subject: Re: [ft] Freetype2 compilation error >>> >>> Dear Amit, >>> >>> Thank you very much for posting the result of testing tarball. >>> I think the compiled FreeType2 binary will work on the platform >>> that you executed the configure, but its header files should not >>> be shared with different platforms (e.g. sharing the header files >>> between 64-bit systems and 32-bit systems would cause a trouble). >>> Although I'm not sure whether the mixture of 32-bit AIX and 64-bit >>> AIX is popular situation, I wish if FreeType2 could support the >>> shared header file in such case, too. >>> >>> From the messages by testing tarball, I'm afraid that xlc's cpp >>> (/bin/cpp) does not work well with the 64-bit constants in C >>> preprocessor macro. I will post a few other testing codes... >>> Please keep in touch. >>> >>> Regards, >>> mpsuzuki >>> >>> HCL Infosystems Ltd wrote: >>>> Dear mpsuzuki, >>>> >>>> Thanks for the below information. Anyways now i am able to compile >>>> Freetype2. >>>> >>>> Also find the below is the o/p extracted by configure script: >>>> >>>> ###########################################QUOTE########################################### >>>> checking whether cpp computation of bit length in ftconfig.in works... ... >>>> conftest.c is: >>>> ------------------------------------------------------ >>>> #include <limits.h> >>>> #define FT_CONFIG_OPTIONS_H "ftoption.h" >>>> #define FT_CONFIG_STANDARD_LIBRARY_H "ftstdlib.h" >>>> #define FT_UINT_MAX UINT_MAX >>>> #define FT_ULONG_MAX ULONG_MAX >>>> #include "ftconfig.in" >>>> #if FT_SIZEOF_INT == 4 >>>> ac_cpp_ft_sizeof_int=4 >>>> #endif >>>> #if FT_SIZEOF_LONG == 8 >>>> ac_cpp_ft_sizeof_long=8 >>>> #endif >>>> ------------------------------------------------------ >>>> execute /bin/cpp -I. -I. -DFT2_CPP_TESTING conftest.c >>>> result >>>> ------------------------------------------------------ >>>> #line 234 "/usr/include/float.h" >>>> extern unsigned int SINFINITY; >>>> extern unsigned int _DBLINF[2]; >>>> extern unsigned int SQNAN; >>>> extern unsigned int DQNAN[2]; >>>> extern unsigned int SSNAN; >>>> extern unsigned int DSNAN[2]; >>>> #line 265 >>>> typedef unsigned short fprnd_t; >>>> #line 274 >>>> fprnd_t fp_read_rnd(void); >>>> fprnd_t fp_swap_rnd(fprnd_t rnd); >>>> #line 45 "ftconfig.in" >>>> FT_BEGIN_HEADER >>>> #line 182 >>>> typedef signed short FT_Int16; >>>> typedef unsigned short FT_UInt16; >>>> #line 187 >>>> typedef signed int FT_Int32; >>>> typedef unsigned int FT_UInt32; >>>> #line 203 >>>> typedef int FT_Fast; >>>> typedef unsigned int FT_UFast; >>>> #line 538 >>>> FT_END_HEADER >>>> #line 8 "conftest.c" >>>> ac_cpp_ft_sizeof_int=4 >>>> ------------------------------------------------------ >>>> ac_cpp_ft_sizeof_int = 4 >>>> ac_cpp_ft_sizeof_long = >>>> :ft_use_autoconf_sizeof_types:enable_biarch_config:=:yes:: >>>> checking whether cpp computation of bit length in ftconfig.in works... no >>>> checking for stdlib.h... (cached) yes >>>> checking for unistd.h... (cached) yes >>>> ###########################################UNQUOTE########################################### >>>> >>>> Regards >>>> Amit >>>> >>>> ----- Original Message ----- >>>> From: "suzuki toshiya" <[email protected]> >>>> To: "HCL Infosystems Ltd" <[email protected]> >>>> Cc: "Werner LEMBERG" <[email protected]>, "freetype" <[email protected]> >>>> Sent: Tuesday, March 19, 2013 3:53:47 PM >>>> Subject: Re: [ft] Freetype2 compilation error >>>> >>>> Dear Amit, >>>> >>>> Thank you very much for kind accept. >>>> I uploaded yet another testing tarball, >>>> http://gyvern.ipc.hiroshima-u.ac.jp/~mpsuzuki/freetype-2.4.11_fix-for-xlc-cpp_20130319b.tar.xz >>>> >>>> Its configure prints additional information about the integer >>>> size checking by cpp, as following. Please post the messages >>>> generated by configure script. In this time, no need to post >>>> config.log. Thanks in advance! >>>> >>>> # I phoned to IBM Japan and ask whether they still provide >>>> # "porting centre" servicesthat they had ever provided >>>> # 10 years ago, for the developers porting the softwares onto >>>> # AIX. Unfortunately, they replied the current service is only >>>> # for the software companies, so the people from public sectors >>>> # or research institute could not use :-( >>>> >>>> Regards, >>>> mpsuzuki >>>> >>>> -- >>>> >>>> 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... ... >>>> conftest.c is: >>>> ------------------------------------------------------ >>>> #include <limits.h> >>>> #define FT_CONFIG_OPTIONS_H "ftoption.h" >>>> #define FT_CONFIG_STANDARD_LIBRARY_H "ftstdlib.h" >>>> #define FT_UINT_MAX UINT_MAX >>>> #define FT_ULONG_MAX ULONG_MAX >>>> #include "ftconfig.in" >>>> #if FT_SIZEOF_INT == 4 >>>> ac_cpp_ft_sizeof_int=4 >>>> #endif >>>> #if FT_SIZEOF_LONG == 8 >>>> ac_cpp_ft_sizeof_long=8 >>>> #endif >>>> ------------------------------------------------------ >>>> execute gcc -E -I. -I. -DFT2_CPP_TESTING conftest.c >>>> result >>>> ------------------------------------------------------ >>>> # 1 "conftest.c" >>>> # 1 "<built-in>" >>>> # 1 "<command-line>" >>>> # 1 "conftest.c" >>>> # 1 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 1 3 4 >>>> # 34 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 3 4 >>>> # 1 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/syslimits.h" 1 3 4 >>>> >>>> >>>> >>>> >>>> >>>> >>>> # 1 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 1 3 4 >>>> # 169 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 3 4 >>>> # 1 "/usr/include/limits.h" 1 3 4 >>>> # 27 "/usr/include/limits.h" 3 4 >>>> # 1 "/usr/include/features.h" 1 3 4 >>>> # 323 "/usr/include/features.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/predefs.h" 1 3 4 >>>> # 324 "/usr/include/features.h" 2 3 4 >>>> # 356 "/usr/include/features.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/sys/cdefs.h" 1 3 4 >>>> # 359 "/usr/include/x86_64-linux-gnu/sys/cdefs.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/wordsize.h" 1 3 4 >>>> # 360 "/usr/include/x86_64-linux-gnu/sys/cdefs.h" 2 3 4 >>>> # 357 "/usr/include/features.h" 2 3 4 >>>> # 388 "/usr/include/features.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/gnu/stubs.h" 1 3 4 >>>> >>>> >>>> >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/wordsize.h" 1 3 4 >>>> # 5 "/usr/include/x86_64-linux-gnu/gnu/stubs.h" 2 3 4 >>>> >>>> >>>> >>>> >>>> # 1 "/usr/include/x86_64-linux-gnu/gnu/stubs-64.h" 1 3 4 >>>> # 10 "/usr/include/x86_64-linux-gnu/gnu/stubs.h" 2 3 4 >>>> # 389 "/usr/include/features.h" 2 3 4 >>>> # 28 "/usr/include/limits.h" 2 3 4 >>>> # 145 "/usr/include/limits.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/posix1_lim.h" 1 3 4 >>>> # 157 "/usr/include/x86_64-linux-gnu/bits/posix1_lim.h" 3 4 >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/local_lim.h" 1 3 4 >>>> # 39 "/usr/include/x86_64-linux-gnu/bits/local_lim.h" 3 4 >>>> # 1 "/usr/include/linux/limits.h" 1 3 4 >>>> # 40 "/usr/include/x86_64-linux-gnu/bits/local_lim.h" 2 3 4 >>>> # 158 "/usr/include/x86_64-linux-gnu/bits/posix1_lim.h" 2 3 4 >>>> # 146 "/usr/include/limits.h" 2 3 4 >>>> >>>> >>>> >>>> # 1 "/usr/include/x86_64-linux-gnu/bits/posix2_lim.h" 1 3 4 >>>> # 150 "/usr/include/limits.h" 2 3 4 >>>> # 170 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 2 3 4 >>>> # 8 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/syslimits.h" 2 3 4 >>>> # 35 "/usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed/limits.h" 2 3 4 >>>> # 2 "conftest.c" 2 >>>> >>>> >>>> >>>> >>>> # 1 "ftconfig.in" 1 >>>> # 40 "ftconfig.in" >>>> # 1 "./ft2build.h" 1 >>>> # 41 "ftconfig.in" 2 >>>> # 1 "ftoption.h" 1 >>>> # 42 "ftconfig.in" 2 >>>> # 1 "ftstdlib.h" 1 >>>> # 43 "ftconfig.in" 2 >>>> >>>> >>>> FT_BEGIN_HEADER >>>> # 182 "ftconfig.in" >>>> typedef signed short FT_Int16; >>>> typedef unsigned short FT_UInt16; >>>> >>>> >>>> >>>> typedef signed int FT_Int32; >>>> typedef unsigned int FT_UInt32; >>>> # 203 "ftconfig.in" >>>> typedef int FT_Fast; >>>> typedef unsigned int FT_UFast; >>>> # 270 "ftconfig.in" >>>> /undef >>>> /undef long >>>> # 538 "ftconfig.in" >>>> FT_END_HEADER >>>> # 7 "conftest.c" 2 >>>> >>>> ac_cpp_ft_sizeof_int=4 >>>> >>>> >>>> ac_cpp_ft_sizeof_long=8 >>>> ------------------------------------------------------ >>>> ac_cpp_ft_sizeof_int = 4 >>>> ac_cpp_ft_sizeof_long = 8 >>>> :ft_use_autoconf_sizeof_types:enable_biarch_config:=::: >>>> checking whether cpp computation of bit length in ftconfig.in works... yes >>>> >>>> >>>> HCL Infosystems Ltd wrote: >>>>> Yes please fix it. >>>>> >>>>> Regards >>>>> Amit >>>>> >>>>> ----- Original Message ----- >>>>> From: "suzuki toshiya" <[email protected]> >>>>> To: "freetype" <[email protected]> >>>>> Cc: "HCL Infosystems Ltd" <[email protected]>, "Werner LEMBERG" >>>>> <[email protected]> >>>>> Sent: Tuesday, March 19, 2013 2:40:34 PM >>>>> Subject: Re: [ft] Freetype2 compilation error >>>>> >>>>> Dear Amit, >>>>> >>>>> Thanks, hmm, ftconfig.in does not work well on AIX+XLC. >>>>> >>>>>> configure:4216: checking whether cpp computation of bit length in >>>>>> ftconfig.in works >>>>>> configure:4280: result: no >>>>> I want to fix it to "yes" :-), so I would ask further >>>>> testing in later, if you can accept... >>>>> >>>>> Regards, >>>>> mpsuzuki >>>>> >>>>> HCL Infosystems Ltd wrote: >>>>>> Please find the attachment. >>>>>> >>>>>> Regards >>>>>> Amit >>>>>> >>>>>> ----- Original Message ----- >>>>>> From: "suzuki toshiya" <[email protected]> >>>>>> To: "HCL Infosystems Ltd" <[email protected]> >>>>>> Cc: "Werner LEMBERG" <[email protected]>, "freetype" <[email protected]> >>>>>> Sent: Tuesday, March 19, 2013 1:42:34 PM >>>>>> Subject: Re: [ft] Freetype2 compilation error >>>>>> >>>>>> 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" <[email protected]> >>>>>>> To: "freetype" <[email protected]> >>>>>>> Cc: "HCL Infosystems Ltd" <[email protected]>, "Werner >>>>>>> LEMBERG" <[email protected]> >>>>>>> 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" <[email protected]> >>>>>>>>> To: "HCL Infosystems Ltd" <[email protected]> >>>>>>>>> Cc: [email protected] >>>>>>>>> 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 >>>>>>>>>> [email protected] >>>>>>>>>> https://lists.nongnu.org/mailman/listinfo/freetype >>>>>>>> _______________________________________________ >>>>>>>> Freetype mailing list >>>>>>>> [email protected] >>>>>>>> https://lists.nongnu.org/mailman/listinfo/freetype >> >> >> [Text Documents:cpp-bitshift-test.c] >> > > > > [Text Documents:cpp-bitshift-test2.c] > _______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
