unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@ni.aist.go.jp>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; Problems with Apple's libXft and configure
Date: Fri, 01 Feb 2008 20:51:39 +0900	[thread overview]
Message-ID: <E1JKuQl-0004i8-Mw@etlken.m17n.org> (raw)
In-Reply-To: <E4DE41FF-A984-46E2-899F-97CD11962ECF@Freenet.DE> (message from Peter Dyballa on Fri, 1 Feb 2008 10:28:57 +0100)

In article <E4DE41FF-A984-46E2-899F-97CD11962ECF@Freenet.DE>, Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> No. Since many weeks, maybe months, I have the X resource

> 	Emacs.FontBackend:      x

> set or I launch GNU Emacs with --disable-font-backend. So I can  
> configure with '--enable-font-backend --with-xft.' When I make

> 	Emacs.FontBackend:      xft

> active GNU Emacs 23.0.60 crashes after a few seconds with

> 	Fatal error (11)Segmentation fault
> 	Exit 139

> when I launch it without --disable-font-backend. So libXft still  
> cannot be used for font rendering (though it works in Apple's xterm).  
> I could use it last summer (or autumn ?) last time, but the results  
> were not recognised as an improvement and documentation is so sparse  
> that I did not see a chance to make it look better, make it use my  
> preferred font.

Please try to configure Emacs with --enable-font-backend
and --without-xft, and set this resource:
Emacs.FontBackend: ftx

With this setting, Emacs uses Freetype directly.

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-02-01 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  0:30 23.0.60; Problems with Apple's libXft and configure Peter Dyballa
2008-01-31 13:39 ` Peter Dyballa
2008-02-01  5:10   ` Kenichi Handa
2008-02-01  9:28     ` Peter Dyballa
2008-02-01 11:51       ` Kenichi Handa [this message]
2008-02-01 14:04         ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JKuQl-0004i8-Mw@etlken.m17n.org \
    --to=handa@ni.aist.go.jp \
    --cc=Peter_Dyballa@Freenet.DE \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).