[texworks] fontconfig issues

Jonathan Kew jonathan at jfkew.plus.com
Sat Sep 27 11:59:10 CEST 2008

On 26 Sep 2008, at 11:43 PM, SGMOYE at mac.com wrote:

> Well, that worked perfectly, so I returned with eager anticipation  
> to Xcode and TeXworks -- and got the same warning and four errors.  
> If I knew how to do do a hollow laugh, I'd do one now... 8>}
> I'm going to leave this until Monday: All of this has taken place at  
> work at the AMS, so when I return to work on Monday -- all  
> rejuvenated -- I'll try to nail this down.

For Monday: did you remember to "sudo make install" your new hunspell  
library, or is the one in /usr/local/lib still the old single-platform  

What does

     file /usr/local/lib/libhunspell-1.2.dylib

report? If you've got a Universal lib, it should say something like

     /usr/local/lib/libhunspell-1.2.dylib: Mach-O universal binary  
with 2 architectures
     /usr/local/lib/libhunspell-1.2.dylib (for architecture ppc7400):	 
Mach-O dynamically linked shared library ppc
     /usr/local/lib/libhunspell-1.2.dylib (for architecture i386):	 
Mach-O dynamically linked shared library i386

Did you quit Xcode (and perhaps even regenerate the project with qmake  
for good measure), in case it was "remembering" something it shouldn't?

> It's odd: compiling TeXworks on Ubuntu was a snap, but with the Mac  
> OS it is a real challenge. Go figure.

Two reasons: (1) building poppler for a non-X11 environment isn't all  
that well supported, and (2) you're trying to do a universal binary,  
but not all libraries are set up to do that by default. If you remove  
the dual-architecture setting from the project file, I suspect it'd  
build much more easily.


More information about the texworks mailing list