public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: kxn30@po.cwru.edu
To: guile-emacs@sourceware.cygnus.com
Subject: Re: Failure of compiling
Date: Thu, 14 Sep 2000 08:31:00 -0000	[thread overview]
Message-ID: <20000915003105V.saka@yugen.org> (raw)
In-Reply-To: <m3itrzq3l9.fsf@indy.STUDENT.CWRU.Edu>

>>>>> In < m3itrzq3l9.fsf@indy.STUDENT.CWRU.Edu > 
>>>>>	Keisuke Nishida <kxn30@po.cwru.edu> wrote:

> > The following patch included in the MULE 4.1 patch causes the
> > above error, since I successed in building guile-emacs after I
> > applied it against mule-conf.el in reverse.

> Okay, what you need is to apply the MULE 4.1 patch to guile-emacs's src
> directory, too.  Try the following:

>   % cd guile-emacs
>   % sed -n '/callproc/,//p' emacs-20.7-mule-4.1.patch | patch -p1
>   % configure && make install

I tried it. Then, I succeeded in building guile-emacs by MULE 4.1
without any errors and warnings :-)

Guile-emacs built by MULE 4.1 works out around Mule-UCS and the
coding-systems.

| Well..., guile-emacs seems to work good for me. Wanderlust, a
| mail/news reader, can work on it. There are a few problems only
| around Mule-UCS and coding-systems relative with
| Unicode/ISO-10646 as far as I notice.

Thanks a lot!

-- 
SAKA Toshihide
P.S. I am writing this message by Wanderlust on Guile-Emacs/MULE 4.1.

      reply	other threads:[~2000-09-14  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-12  7:13 
2000-09-12 13:33 ` Keisuke Nishida
2000-09-12 21:18   ` kxn30
2000-09-12 21:52     ` Keisuke Nishida
2000-09-12 23:36       ` kxn30
2000-09-13 10:45         ` Keisuke Nishida
2000-09-13 11:41           ` kxn30
2000-09-13 16:23         ` Keisuke Nishida
2000-09-14  8:31           ` kxn30 [this message]

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

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

  git send-email \
    --in-reply-to=20000915003105V.saka@yugen.org \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.com \
    /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.
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).