public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: linux-kbuild@vger.kernel.org
Cc: Michal Marek <mmarek@suse.cz>
Subject: Translating a .S to a .c and back fails
Date: Mon, 27 Sep 2010 21:00:27 -0700	[thread overview]
Message-ID: <4CA1685B.1000601@codeaurora.org> (raw)

 I've recently posted a patch to translate ARM's delay.S in arch/arm/lib
into a C file[1]. This works fine and I can build the tree with the .S
file and then build the tree with the .C file. After I do that I can't
switch back to the .S version of the tree without first removing the
.delay.o.cmd file in my build output directory. It seems that the build
system can't recognize when a C file turns into an assembly file.

Anyone else seen this problem? I admit it is pretty rare, but it becomes
annoying with things like automated building, bisecting, etc. where I
don't make clean all the time.

[1] http://lkml.org/lkml/2010/9/27/605

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


                 reply	other threads:[~2010-09-28  4:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CA1685B.1000601@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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