mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Kernel Developer List <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6 build oddity...
Date: Sun, 22 Feb 2004 22:03:49 +0100	[thread overview]
Message-ID: <20040222210349.GA14932@mars.ravnborg.org> (raw)
In-Reply-To: <20040222081959.GA21170@one-eyed-alien.net>

On Sun, Feb 22, 2004 at 12:19:59AM -0800, Matthew Dharm wrote:
> I'm not sure where to report this....
> 
> In some sort of freak accident, I had a .s file in my source tree.
> Whenever I did a build (make bzImage modules), the build process would:
> (1) check out the corresponding .c file
> (2) build the .s into the .o
> (3) delete the .c file

I have tried to reproduce this locally (with 2.6 kernel btw).
make
make kernel/pid.s
rm kernel/pid.c

And as you tell, the .c file is checked out. But I can here that
also the .c file is used when compiling pid.o.

Care to provide a few more details, such as:

- Kernel version
- What file is was
- What SCM you are using (uses bk here)
- Full log of what is happening (off-list is fine)

	Sam

> Which I find odd, because:
> (1) It never used the .c file, but checked it out anyway
> (2) It _did_ delete the .c file, without using it
> 
> Matt
> 
> -- 
> Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
> Maintainer, Linux USB Mass Storage Driver
> 
> G:  Let me guess, you started on the 'net with AOL, right?
> C:  WOW! d00d! U r leet!
> 					-- Greg and Customer 
> User Friendly, 2/12/1999



-- 

      reply	other threads:[~2004-02-22 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  8:19 Matthew Dharm
2004-02-22 21:03 ` Sam Ravnborg [this message]

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=20040222210349.GA14932@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®