> > The fontconfig segfault happens with any of the 2.1.92-2, 2.2.0-2 or > > 2.2.0-5 versions of fontconfig/libfontconfig on kullervo. > > Ok, that would at first glance appear to void my hypothesis; however, > fontconfig uses freetype, and that could have been miscompiled. Can you
Indeed, all freetype/libfreetype combos did work fine with libfreetype6_2.1.4-1_m68k.deb and libfreetype6_2.1.4-2_m68k.deb from the apt cache. bash-2.05b# ldd /usr/lib/libfreetype.so.6.3.3 (-1) libz.so.1 => /lib/libz.so.1 (0xc004d000) libc.so.6 => /lib/libc.so.6 (0xc005b000) /lib/ld.so.1 => /lib/ld.so.1 (0xd0000000) bash-2.05b# ldd /usr/lib/libfreetype.so.6.3.3 (-2) libz.so.1 => /lib/libz.so.1 (0xc004e000) libc.so.6 => /lib/libc.so.6 (0xc005c000) /lib/ld.so.1 => /lib/ld.so.1 (0xd0000000) libfreetype6_2.1.4-4_m68k.deb makes fc-cache core dump. bash-2.05b# ldd /usr/lib/libfreetype.so.6.3.3 libz.so.1 => /lib/libz.so.1 (0xc004d000) libc.so.6 => /lib/libc.so.6 (0xc005b000) /lib/ld.so.1 => /lib/ld.so.1 (0xd0000000) strings /usr/lib/libfreetype.so.6.3.3 | grep GCC doesn't show anything, how do I determine which gcc it was built with? > try also downgrading that to a pre gcc-3.3 version? > > What I really need is a gdb backtrace with debugging information. Seems the libfreetype guy would need all that now, no? m68k-build: Where shall I put libfreetype6_2.1.4-2_m68k.deb ?? Michael