All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corneliu ZUZU <czuzu@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tamas K Lengyel <tamas@tklengyel.com>, Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: EXTRA_CFLAGS when compiling Xen
Date: Wed, 17 Feb 2016 14:09:43 +0200	[thread overview]
Message-ID: <56C46307.1060303@bitdefender.com> (raw)
In-Reply-To: <56C45ACD02000078000D3076@prv-mh.provo.novell.com>

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
> achieve this by invoking make from the top level directory -
> you need to run make directly in xen/ and manually specify
> the intended target (including leading sub-directories).
>
> Jan
>

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?
This is not so important since for now Razvan's suggestion does the 
trick (or adding %.i as a dependency for %.o in Rules.mk),
but I thought it would be nice for future reference, so only respond 
when/if you have the time/disposition.

Thanks,
Corneliu.

  reply	other threads:[~2016-02-17 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 10:19 EXTRA_CFLAGS when compiling Xen Corneliu ZUZU
2016-02-17 10:23 ` Razvan Cojocaru
2016-02-17 10:34   ` Corneliu ZUZU
2016-02-17 10:34 ` Jan Beulich
2016-02-17 12:09   ` Corneliu ZUZU [this message]
2016-02-17 12:43     ` Jan Beulich
2016-02-17 13:11       ` Corneliu ZUZU
2016-02-17 13:54         ` Jan Beulich
2016-02-17 17:09           ` Corneliu ZUZU
2016-02-17 17:02     ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C46307.1060303@bitdefender.com \
    --to=czuzu@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=rcojocaru@bitdefender.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tamas@tklengyel.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.