This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gcc-3.4-20050401 BUG? generates illegal instruction in X11R6.4.2/mkfontscale/freetypemacro


Hello, gcc-list!
Hello, Melchior!

Well, about a year ago, we/you have had problems when building X11
that mkfontscale crashes with an illegal instruction or an segmentation
fault on powerpc. Maybe some of you remember.

Here is the old mail:
[Devel] [BUG] freetype2 CVS/HEAD: crash in FT_Get_Name_Index (ftobjs.c:2407)
http://lists.gnu.org/archive/html/freetype-devel/2004-04/msg00051.html

I am running into the same problems again (and several others did).
Even with a pretty new toolchain:
gcc-3.4-20050401 (3.4.4)
X11R6.4.2
glibc-2.3.4
binutils-2.15.96
freetype-2.1.9

to reproduce the problem:
install freetype-2.1.9
	./configure
	make
	make install
compile X
	make World
everything fine
	make install

when mkfontscale tries to
+ ../../../exports/bin/mkfontscale /usr/X11R6/lib/X11/fonts/Type1
make[4]: *** [install] Error 132
(Illegal instruction)

I ran into the same problem again and again. This only happens
with the Type1 fonts... the others build fine!

My host is a embedded PowerPC from Freescale (MPC8540, e500 core, no fpu)

I've applied your patch for the macro. (inserting a dummy printf("");)
But this doesn't fix the problem on my platform.
What is the real background that mkfontscale breaks?
A compiler error or a bug in freetype?

Are there any good news that the problem is really fixed?
Well... and how? Any suggestions to track down that problem?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]