public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How build dependencies work/are supposed to work in 2.5
Date: Fri, 10 Jan 2003 19:03:38 +0100	[thread overview]
Message-ID: <CD9EA6E65DF@vcnet.vc.cvut.cz> (raw)

On 10 Jan 03 at 18:35, Sam Ravnborg wrote:
> On Thu, Jan 09, 2003 at 11:33:32PM +0100, Petr Vandrovec wrote:
> >   So I'd like to ask whether current kernel build system is supposed
> > to track changes in include files automagically, or whether I'm supposed
> > to run 'make dep' from time to time?
> 
> Until now I'm only aware of one set of problems that kbuild does not
> handle correct. That is when the timestamp of the files goes backward.
> This happens at least in the following situations:
> 1) A file is saved, and mv is used to restore the original
> 2) CVS is configured to preserve original timestamp when files are 'dumped'
> 3) NFS mounted filesystems where the clock is wrong. Timezone
>    inconsistency for eaxmple.
> 
> I assume you were hit by some flavour of 1) ???

Thanks for your explanation. After I was thinking about it, you are 
probably right. Maybe that I just copied console_struct.h from 
distribution kernel instead of reverting patch to get to the original
version, and I forgot touching file.

Sorry for confusion.
                                            Thanks,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
                                                

                 reply	other threads:[~2003-01-10 17:54 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=CD9EA6E65DF@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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