From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.bugs Subject: bug#14644: emacsclient.c fails to compile Date: Tue, 18 Jun 2013 15:37:22 -0400 Message-ID: References: <51C01357.3000000@cs.ucla.edu> <83d2rjs8qr.fsf@gnu.org> <83mwqnqkmg.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1371584288 27563 80.91.229.3 (18 Jun 2013 19:38:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Jun 2013 19:38:08 +0000 (UTC) Cc: eggert@cs.ucla.edu, 14644@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jun 18 21:38:07 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Up1jC-0006vN-NC for geb-bug-gnu-emacs@m.gmane.org; Tue, 18 Jun 2013 21:38:06 +0200 Original-Received: from localhost ([::1]:56849 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up1jC-0005pt-Bx for geb-bug-gnu-emacs@m.gmane.org; Tue, 18 Jun 2013 15:38:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up1j9-0005pE-Nj for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2013 15:38:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Up1j8-0002np-RL for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2013 15:38:03 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:59456) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up1j8-0002nl-P7 for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2013 15:38:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Up1j8-0007tS-1p for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2013 15:38:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Glenn Morris Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 18 Jun 2013 19:38:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14644 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 14644-submit@debbugs.gnu.org id=B14644.137158424630268 (code B ref 14644); Tue, 18 Jun 2013 19:38:01 +0000 Original-Received: (at 14644) by debbugs.gnu.org; 18 Jun 2013 19:37:26 +0000 Original-Received: from localhost ([127.0.0.1]:53772 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Up1iY-0007s6-2M for submit@debbugs.gnu.org; Tue, 18 Jun 2013 15:37:26 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:50108 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Up1iW-0007rz-I5 for 14644@debbugs.gnu.org; Tue, 18 Jun 2013 15:37:24 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Up1iV-0004Td-4R; Tue, 18 Jun 2013 15:37:23 -0400 X-Spook: benelux red noise Juiliett Class Submarine government X-Ran: }h,9QI3n"+lKJ{Mr_LJPg+[#OG^zWKc:paTAe" X-Hue: blue X-Attribution: GM In-Reply-To: <83mwqnqkmg.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Jun 2013 22:33:43 +0300") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:75310 Archived-At: Eli Zaretskii wrote: > Shouldn't .deps/getopt.Po catch that? No idea. :) I'm just idly speculating in total ignorance of the details. I imagine make clean will fix it, and involve a lot less CPU time than any brain time we might spend trying to figure out exactly what goes on.