From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: William Xu Newsgroups: gmane.emacs.bugs Subject: Re: make for emacs fails under OS X 10.5 Date: Sat, 03 Nov 2007 13:46:57 +0900 Organization: the Church of Emacs Message-ID: References: <93DF8565-CAA3-4D03-949D-2B8BF6C5B812@mac.com> <1193874260.518817.155790@z24g2000prh.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1194065256 22998 80.91.229.12 (3 Nov 2007 04:47:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Nov 2007 04:47:36 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Nov 03 05:47:39 2007 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IoAv5-0003gs-9g for geb-bug-gnu-emacs@m.gmane.org; Sat, 03 Nov 2007 05:47:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoAuv-0001Sp-4l for geb-bug-gnu-emacs@m.gmane.org; Sat, 03 Nov 2007 00:47:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IoAuj-0001Ke-4Y for bug-gnu-emacs@gnu.org; Sat, 03 Nov 2007 00:47:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IoAuh-0001IL-9f for bug-gnu-emacs@gnu.org; Sat, 03 Nov 2007 00:47:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoAuh-0001ID-2g for bug-gnu-emacs@gnu.org; Sat, 03 Nov 2007 00:47:15 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IoAug-0007t7-HC for bug-gnu-emacs@gnu.org; Sat, 03 Nov 2007 00:47:14 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IoAuW-00016P-TC for bug-gnu-emacs@gnu.org; Sat, 03 Nov 2007 04:47:04 +0000 Original-Received: from khp059140005246.ppp-bb.dion.ne.jp ([59.140.5.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Nov 2007 04:47:04 +0000 Original-Received: from william.xwl by khp059140005246.ppp-bb.dion.ne.jp with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Nov 2007 04:47:04 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: khp059140005246.ppp-bb.dion.ne.jp User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (darwin) Cancel-Lock: sha1:JCVO0kG8yPYzU/Xo33FpFtmn6a8= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:16900 Archived-At: Ted Zlatanov writes: > This has been reported to the emacs-devel mailing list repeatedly. It > was probably introduced with the Unicode merge in August. Hmm, i'm running it happily now with: ,----[ emacs-version ] | GNU Emacs 23.0.50.9 (powerpc-apple-darwin8.10.0, Carbon Version 1.6.0) | of 2007-10-20 on enjoy-life `---- I built it on osx 10.4.10, with option, `--prefix=$HOME --with-carbon --without-x'. And the other thing is that i disable the fink in the `configure' file by applying nofink.patch from carbon emacs 22.1. (since i couldn't even bootstrap emacs with fink, and i also don't understand why people refuse to remove it) So i guess the slow responsiveness is introduced either by recent cvs changes(20071020 - now) or osx changes(10.4 -> 10.5). Since I built cvs emacs regularly, looks like i could still run cvs emacs built after 20071020, but i couldn't remember the exact revision that introduced this problem. (And i have no osx 10.4 anymore..) -- William