Re: [ft-devel] Bug on PowerPC: Illegal Intruction in FT_Get_Name_Index (worksforme)

[Behdad Esfahbod]

I you compile with all warnings on (-Wall), do you get a message
about strict-aliasing?

behdad


On Mon, 11 Apr 2005, Clemens Koller wrote:

> Hello, Christian!
> (please post to the list also...)
>
> Okay, that was a good point:
>
> In an old changelog, Christian found:
> http://rpm.sh-linux.org/rpm-index-2004/sh4/freetype-devel-2.1.7-4.sh4.html
>
>  >  Wed Mar 10 2004 Mike A. Harris <address@hidden> 2.1.7-3
>  >   - Added -fno-strict-aliasing to CFLAGS and CXXFLAGS to try to fix SEGV 
> and
>  >     SIGILL crashes in mkfontscale which have been traced into freetype and 
> seem
>  >     to be caused by aliasing issues in freetype macros (#118021)
>
> Okay, here is my latest buildlog:
>
>       cd <..>/freetype-2.1.9
>       export CFLAGS=-fno-strict-aliasing
>       export CXXFLAGS=-fno-strict-aliasing
>       (export DEBUG_HINTER=                   enables debugging and tests? 
> (see makefiles))
>       ./configure --prefix=/usr
>       make
>       su
>       make install
>       cd <..>/xc/programs/mkfontscale
>       make clean
>       make
>       ls -l Type1
>               -rw-r--r--    1 clemens  users       75363 Apr  9 21:11 
> UTBI____.pfa
>       ./mkfontscale Type1
>       less Type1/fonts.scale
>               3
>               UTBI____.pfa -adobe-utopia-bold-i-normal--0-0-0-0-p-0-ascii-0
>               UTBI____.pfa -adobe-utopia-bold-i-normal--0-0-0-0-p-0-iso10646-1
>               UTBI____.pfa -adobe-utopia-bold-i-normal--0-0-0-0-p-0-iso8859-1
>
> Voila! mkfontscale works!
> The solution use -fno-strict-aliasing
>
> There are more references to this problem:
> http://lists.freedesktop.org/pipermail/x-packagers/2004-March/000010.html
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118021
>
> So, my conclusion is (read the bugzilla report) that there still might
> be a bug either in freetype or in gcc.
>
> So, what's next? Do you consider to patch the makefiles (Jamfiles)
> of freetype if we build on <some special>-ppc32 platforms?
> Why does it fail if I don't use -fno-strict-aliasing?
>
> Currently, this is in a -works-for-me- state!
>
> Best greets,
>
> Clemens Koller
> _______________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Str. 45/1
> 81379 Muenchen
> Germany
>
> http://www.anagramm.de
> Phone: +49-89-741518-50
> Fax: +49-89-741518-19
>
> Christian Demmer wrote:
>  > Guten Tag,
>  >
>  > ich habe gerade nochmal ein bißchen rumgesucht, dabei habe ich in:
>  > <http://rpm.sh-linux.org/rpm-index-2004/sh4/freetype-devel-2.1.7-4.sh4.
>  > html>
>  >
>  > folgendes gefunden:
>  >
>  >  Wed Mar 10 2004 Mike A. Harris <address@hidden> 2.1.7-3
>  >   - Added -fno-strict-aliasing to CFLAGS and CXXFLAGS to try to fix SEGV 
> and
>  >     SIGILL crashes in mkfontscale which have been traced into freetype and 
> seem
>  >     to be caused by aliasing issues in freetype macros (#118021)
>  >
>  > Vielleicht ist es einen Versuch wert.
>  >
>  > Viele Grüße, Christian
>  >
>
>
>
>
> _______________________________________________
> Freetype-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/freetype-devel
>
>

--behdad
http://behdad.org/