[tex-live] compilation error with graphite-engine/src/font/Font.cpp

[Jonathan Kew]

On 7 Mar 2008, at 11:13 am, Peter Münster wrote:

> Excuse me please, my last email wasn't complete...
>
> Hello,
>
> I get the following compilation error on my Linux-i586 system:
>
>  g++ -DPACKAGE_NAME=\"silgraphite\" -DPACKAGE_TARNAME=\"silgraphite\"
>  -DPACKAGE_VERSION=\"2.3\" "-DPACKAGE_STRING=\"silgraphite 2.3\""
>  -DPACKAGE_BUGREPORT=\"silgraphite-devel at lists.sourceforge.net\"
>  -DPACKAGE=\"silgraphite\" -DVERSION=\"2.3\" -DSTDC_HEADERS=1
>  -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
>  -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 - 
> DHAVE_INTTYPES_H=1
>  -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1
>  -DSIZEOF_WCHAR_T=4 -DHAVE_FABSF=1
>  -I. -I../../../../libs/graphite-engine/src
>  -I../../../../libs/graphite-engine/include/graphite
>  -I../../../../libs/graphite-engine/src/generic
>  -I../../../../libs/graphite-engine/src/font
>  -I../../../../libs/graphite-engine/src/segment -g -O2 -DNDEBUG -Wall
>  -Wno-unknown-pragmas -Wparentheses -Werror -DTRACING -O3 -DNDEBUG -MT
>  Font.lo -MD -MP -MF .deps/Font.Tpo -c
>  ../../../../libs/graphite-engine/src/font/Font.cpp -o Font.o
> cc1plus: warnings being treated as errors
> ../../../../libs/graphite-engine/src/font/Font.cpp: In member function
> 'gr::isocode gr::LanguageIterator::operator*()':
> ../../../../libs/graphite-engine/src/font/Font.cpp:876: error: array
> subscript is above array bounds
> make[2]: *** [Font.lo] Error 1
> make[2]: Leaving directory
> `/usr/src/packages/BUILD/texlive-6874/Build/source/work/libs/ 
> graphite-engine/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/usr/src/packages/BUILD/texlive-6874/Build/source/work/libs/ 
> graphite-engine'
> make: *** [all] Error 1
>
>
> Strange: on another system, Linux-x86_64, there is no such problem.

Looks like your compiler on Linux-i586 is stricter (newer gcc  
version?). It's right; the code is wrong, though that's a branch of  
the conditional that should never actually be used.

>
> Do you have any idea how to solve this one?
>
> TIA for any help!

I have just checked in the fix.

JK