unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: A very strange thing about Emacs working with flyspell!
Date: Mon, 20 Nov 2006 17:44:16 +0900	[thread overview]
Message-ID: <E1Gm4lE-00077q-00@etlken> (raw)
In-Reply-To: <20061120053240.GB12383@localdomain> (message from Hongsheng on Mon, 20 Nov 2006 13:32:40 +0800)

In article <20061120053240.GB12383@localdomain>, Hongsheng <zhaohscas@yahoo.com.cn> writes:

> [1  <text/plain; us-ascii (7bit)>]
> > > (gdb) br xic_create_fontset
> > > Function "xic_create_fontset" not defined.
> > > Make breakpoint pending on future shared library load? (y or [n]) y
> > 
> > ??? This means that xic_create_fontset is not compiled into
> > your Emacs, and that means that HAVE_X_I18N is not defined
> > in your src/config.h.  Can you use SCIM if you run Emacs
> > without --enable-font-backend?

> Yes, I can.

> BTW, when compiling the Emacs, I configured the Emacs with the following arguments:

> ===============
> ./configure --prefix=/usr \
> --x-includes=/usr/include/X11 --x-libraries=/usr/lib/X11 \
> --enable-font-backend --enable-asserts \
> --enable-locallisppath=/usr/share/emacs/site-lisp:/etc/emacs-snapshot/site-start.d
> \
> --enable-largefile --with-pop --with-sound \
> --with-x=yes --with-x-toolkit=gtk --with-toolkit-scroll-bars \
> --with-xpm --with-jpeg --with-tiff --with-gif --with-png \
> --with-freetype  --with-xft --with-xim
> ===============

> > Could you run configure script again and show me the all
> > output and the contents of generated src/config.h.

> See the attachments, please.

I couldn't find any problem with them.  Sigh...

Ok, then how about setting break point as this:

(gdb) br create_frame_xic

and use "s" command to step into the function
xic_create_fontset.

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2006-11-20  8:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061114074507.GA26493@localdomain>
     [not found] ` <E1Gkc7h-0000cx-00@etlken>
     [not found]   ` <20061116113746.GA5373@localdomain>
     [not found]     ` <E1Gl1dE-0004ra-00@etlken>
2006-11-18  2:54       ` A very strange thing about Emacs working with flyspell! zhaohs
2006-11-18  3:04         ` Kenichi Handa
2006-11-18  3:23           ` zhaohs
2006-11-20  2:22             ` Kenichi Handa
2006-11-20  3:04               ` zhaohs
2006-11-20  3:50                 ` Kenichi Handa
2006-11-20  4:05                   ` Hongsheng
2006-11-20  4:22                     ` Kenichi Handa
2006-11-20  5:32                       ` Hongsheng
2006-11-20  8:44                         ` Kenichi Handa [this message]
2006-11-20  9:20                           ` Hongsheng
2006-11-29  2:34                             ` Kenichi Handa
2006-12-04  4:34                               ` Hongsheng

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=E1Gm4lE-00077q-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@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).