While trying to debug the problem with my new build of rxvt-unicode, I
find that I am getting a segfault way down deep in libfreetype. I
rebuilt libfreetype with the new cygport, so I could get those handy
debug symbols, and spent some time trudging thru that.
Then, since libfreetype is actually called by libfontconfig, and not
directly by rxvt-unicode, I decided to download the -src package and
rebuild THAT, too -- again, so I could have debug symbols for a few of
my intervening stack frames.
The (re)build of fontconfig-2.8.0-2 went fine, but when setup installed
it, I got an error during postinstall. Setup.log.full says:
2012/08/28 01:38:48 running: C:\cygwin-1.7\bin\bash.exe --norc
--noprofile "/etc/postinstall/fontconfig.sh"
/etc/postinstall/fontconfig.sh: line 2: 4164 Segmentation fault
(core dumped) /usr/bin/fc-cache -r
Ick. So, I reinstalled the "real" version...and I got the same message:
2012/08/28 01:53:01 running: C:\cygwin-1.7\bin\bash.exe --norc
--noprofile "/etc/postinstall/fontconfig.sh"
/etc/postinstall/fontconfig.sh: line 2: 6856 Segmentation fault
(core dumped) /usr/bin/fc-cache -r
Running 'fc-list : family' also coredumps (using the official
fontconfig-2.8.0-2).
*=-=-=-=-=-=-=-=-=*
I next ran 'fc-cache -fsv' as Adminstrator, and everything went
swimmingly...until I got to the Windows dir:
...
/usr/share/texmf-dist/fonts/type1/urw/times: caching, new cache
contents: 4 fonts, 0 dirs
/usr/share/texmf-dist/fonts/type1/urw/zapfchan: caching, new cache
contents: 1 fonts, 0 dirs
/usr/share/texmf-dist/fonts/type1/urw/zapfding: caching, new cache
contents: 1 fonts, 0 dirs
/cygdrive/c/Windows/Fonts: Segmentation fault (core dumped)
FWIW, I have 469 true type fonts in Windows/Fonts. There are a mixture
of fonts identified by Windows as "TrueType" and "OpenType" even tho
they all end in .ttf. Three of the font files have spaces in their names.
/cygdrive/c/Windows/Fonts/Envy Code R Bold.ttf
/cygdrive/c/Windows/Fonts/Envy Code R Italic.ttf
/cygdrive/c/Windows/Fonts/Envy Code R.ttf
I tried removing those three offenders, just in case, and re-running
fc-cache but it still dumped core.
Any ideas? I'm going to try, just for grins and giggles, installing a
self-built version of fontconfig-2.10.$latest and see if that helps
matters...but I won't be able to do so until Thursday at the earliest.
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
