From mboxrd@z Thu Jan 1 00:00:00 1970 From: Corneliu ZUZU Subject: Re: EXTRA_CFLAGS when compiling Xen Date: Wed, 17 Feb 2016 15:11:06 +0200 Message-ID: <56C4716A.8060808@bitdefender.com> References: <56C4493D.10703@bitdefender.com> <56C45ACD02000078000D3076@prv-mh.provo.novell.com> <56C46307.1060303@bitdefender.com> <56C478E702000078000D31FA@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56C478E702000078000D31FA@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tamas K Lengyel , Keir Fraser , Ian Campbell , Razvan Cojocaru , Andrew Cooper , Xen-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 2/17/2016 2:43 PM, Jan Beulich wrote: >>>> On 17.02.16 at 13:09, wrote: >> On 2/17/2016 12:34 PM, Jan Beulich wrote: >>>> The reason I need this is to pass '-save-temps' to GCC, I want to inspect >>>> some code >>>> and it would be easier to do that on the preprocessed files. >>> ... there's absolutely no need to for a case like this, at least as >>> long as the xen/ subtree is where you want to do this. >>> xen/Rules.mk has rules for what you want (and also for >>> producing the intermediate assembly file), just that you can't >>> achakieve this by invoking me from the top level directory - >>> you need to run make directly in xen/ and manually specify >>> the intended target (including leading sub-directories). >> I wouldn't want to needlessly insist, but of course a canonical way to >> do this would be preferred. >> I do see the %.i targets there in Rules.mk invoking the preprocessor, >> but I haven't yet figured how to make those execute. >> >> Could you detail what make args would activate execution of the %.i targets? > Makes me wonder how the rather detailed reply I've already given > (which also answers this question) hasn't been sufficient. > > Jan > I don't see why there's need for insults when one asks politely. Of course, 'rather detailed' is always a rather subjective assessment. Wonder no more. The original response: * doesn't specify what additional make arguments/environment vars should be set if I'm to run make from ./xen/ rather then ./ * doesn't make it clear what you mean by "intended target". I suppose you weren't suggesting to manually run make for *each* source file I want to preprocess one by one, since I was asking how to do that for all sources ('make dist-xen'...) Thanks anyway, Corneliu.