From: Liu Wang <liuw@supermicro.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: FW: How to let Linux kernel Makefile generate intermediate *.i files ? It doesn't work to add "EXTRA_CFLAGS += -save-temps" in Makefile and gets "cc: warning: -pipe ignored because -wave-temps specified."
Date: Mon, 17 Oct 2011 19:15:00 -0000 [thread overview]
Message-ID: <09F85D53A2F0C547BF5E05E214DB880A23C8563248@MAIL5.supermicro.com> (raw)
-----Original Message-----
From: Liu Wang
Sent: Saturday, October 15, 2011 5:42 PM
To: 'gcc-help@gcc.gnu.org'
Subject: How to let Linux kernel Makefile generate intermediate *.i files ? It doesn't work to add "EXTRA_CFLAGS += -save-temps" in Makefile and gets "cc: warning: -pipe ignored because -wave-temps specified."
Sir./Madam,
Appreciate your helping me with the following.
How to let Linux kernel Makefile generate intermediate *.i files ?
It doesn't work to add "EXTRA_CFLAGS += -save-temps" in Makefile and gets "cc: warning: -pipe ignored because -wave-temps specified."
Sincerely,
Liu Wang
next reply other threads:[~2011-10-17 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 19:15 Liu Wang [this message]
2011-10-17 20:12 ` Randy Dunlap
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=09F85D53A2F0C547BF5E05E214DB880A23C8563248@MAIL5.supermicro.com \
--to=liuw@supermicro.com \
--cc=gcc@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).