From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: /lib/cpp not found in c-mode Date: Tue, 03 May 2005 14:18:11 -0400 Message-ID: References: <17013.26868.207510.370151@farnswood.snap.net.nz> <17013.52411.51878.781739@farnswood.snap.net.nz> <17014.39042.74353.677362@farnswood.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1115232006 17607 80.91.229.2 (4 May 2005 18:40:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 4 May 2005 18:40:06 +0000 (UTC) Cc: nickrob@snap.net.nz, jan.h.d@swipnet.se, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 04 20:40:02 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DTOlY-0000Xb-9c for ged-emacs-devel@m.gmane.org; Wed, 04 May 2005 20:38:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DTOsu-0006mM-Me for ged-emacs-devel@m.gmane.org; Wed, 04 May 2005 14:46:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DT2XY-0001wB-Ae for emacs-devel@gnu.org; Tue, 03 May 2005 14:54:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DT2XR-0001u3-2I for emacs-devel@gnu.org; Tue, 03 May 2005 14:54:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DT2Wn-0001QG-LO for emacs-devel@gnu.org; Tue, 03 May 2005 14:53:53 -0400 Original-Received: from [199.232.41.67] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_ARCFOUR_SHA:16) (Exim 4.34) id 1DT2WX-0000Gq-Oe; Tue, 03 May 2005 14:53:37 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by mx20.gnu.org with esmtp (Exim 4.34) id 1DT1zn-00013B-S4; Tue, 03 May 2005 14:19:48 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 70150340016; Tue, 3 May 2005 14:18:17 -0400 (EDT) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 2DDAB4AC009; Tue, 3 May 2005 14:18:12 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 19DFFE6C1D; Tue, 3 May 2005 14:18:12 -0400 (EDT) Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Tue, 03 May 2005 13:12:42 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.839, requis 5, autolearn=not spam, AWL 0.06, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca 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:36639 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:36639 > Don't know about others, but the reason why I don't use c-macro-expand > is because it basically can't work right without parsing my > Makefile(s) to know which include dirs should be used. And since it > doesn't do that, I've found it of little use. > What information would it need in order to DTRT for you? I'm not sure what you didn't understand, so I'll just rephrase it: in order for the output of cpp to be useful, you need to make sure that all the #include do find the corresponding header file (also it'd be better if the various predefined macros, via -D or built-in into the compiler were handled correctly). This info is in general only available by parsing the Makefile (or equivalent for people who use other tools). Of course I can also manually take the relevant info from the Makefile and put it into c-macro-cppflags, but doing that for each and every project I work on is just too much trouble for me to even try it. Stefan