From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: CVS HEAD fails to build on OSX 10.4 (macterm.c broken?) Date: Fri, 31 Aug 2007 01:12:38 -0700 Message-ID: <200708310812.l7V8Cgq9022040@oogie-boogie.ics.uci.edu> References: <86k5re4blv.fsf@blue.stonehenge.com> <200708291531.l7TFVnlD010335@oogie-boogie.ics.uci.edu> <86fy224aah.fsf@blue.stonehenge.com> <86bqcq4a4q.fsf@blue.stonehenge.com> <200708291604.l7TG4atk011108@oogie-boogie.ics.uci.edu> <867ine492x.fsf@blue.stonehenge.com> <863ay24826.fsf@blue.stonehenge.com> <200708291641.l7TGfo2t012413@oogie-boogie.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1188548160 31525 80.91.229.12 (31 Aug 2007 08:16:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 31 Aug 2007 08:16:00 +0000 (UTC) Cc: "Randal L. Schwartz" , emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 31 10:15:58 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IR1fX-0000KG-2W for ged-emacs-devel@m.gmane.org; Fri, 31 Aug 2007 10:15:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IR1fW-00010t-Fg for ged-emacs-devel@m.gmane.org; Fri, 31 Aug 2007 04:15:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IR1fS-0000x8-Pn for emacs-devel@gnu.org; Fri, 31 Aug 2007 04:15:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IR1fS-0000vG-0l for emacs-devel@gnu.org; Fri, 31 Aug 2007 04:15:50 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IR1fR-0000v6-Tx for emacs-devel@gnu.org; Fri, 31 Aug 2007 04:15:49 -0400 Original-Received: from oogie-boogie.ics.uci.edu ([128.195.1.41]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IR1fR-0008Cq-Fz for emacs-devel@gnu.org; Fri, 31 Aug 2007 04:15:49 -0400 Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by oogie-boogie.ics.uci.edu (8.13.6/8.13.6) with ESMTP id l7V8Cgq9022040; Fri, 31 Aug 2007 01:12:42 -0700 (PDT) In-Reply-To: (YAMAMOTO Mitsuharu's message of "Fri\, 31 Aug 2007 09\:08\:06 +0900") Original-Lines: 40 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-0.41, required 5, autolearn=disabled, ALL_TRUSTED -1.44, FS_OBFU_X 1.03) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-Detected-Kernel: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:77468 Archived-At: YAMAMOTO Mitsuharu writes: > >>>>> On Wed, 29 Aug 2007 09:41:50 -0700, Dan Nicolaescu said: > > >> It works in terminal mode, but fails to launch in carbon mode. :( > > > It used to do at least that much when I did the mac multi-tty port > > back in May. A lot of things seem to have changed in CVS for the mac > > since then. > > Now I can hardly believe that. I couldn't find any calls to > add_keyboard_wait_descriptor in the past macterm.c in the multi-tty > branch despite the comment in process.c below: > > /* Don't do this, it caused infinite select loops. The display > method should call add_keyboard_wait_descriptor on stdin if it > needs that. */ > #if 0 > FD_SET (0, &input_wait_mask); > #endif > > I seriously suspect you ran a wrong (i.e., non multi-tty) executable. I am not sure what your intention is with this. I don't think I had a multi-tty executable around. When I did that work I clearly stated that I did only minimal testing. For the record here's what that meant: -bootstrap with --without-carbon --with-x11, make sure it works -configure --with-carbon -make (no rebootstrap, I kept the byte compiled files) -check that emacs -nw starts up (don't remember what I had to do to make it work, mainly it was compilation fixes for new interfaces) -hack until a carbon frame is displayed, run emacs -f server-start, check that emacsclient and emacsclient -t can connect to it. Given that nobody else cared to make any more changes to the multi-tty carbon port since then, and you stated that you are not interested in maintaining the carbon port for emacs 23, it was probably not a good investment of my time to even go that far.