All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Subject: How build dependencies work/are supposed to work in 2.5.5x
Date: Thu, 9 Jan 2003 23:33:32 +0100	[thread overview]
Message-ID: <CC66A71361E@vcnet.vc.cvut.cz> (raw)

Hi,
  I spent last few hours by patching 2.5.54-bk-something back and 
forward to shrink Juriaans patch which reinstates 2.5.50 fbdev. Sometime
during this course something happened, and I ended up with incorrect
build: some code was thinking that "struct vc_data" contains
"vc_font" element, and some parts believed that there is no such element,
and structure is 24 bytes smaller (shifting vc_origin somewhere, causing
crash during bootup) :-( (there was such element, then there was not,
and then element arrived back during evening)

  After I removed drivers/char/*.o and all .o from drivers/video subtree
and rerun "make", problem disappeared. During patching I never used -T/-Z 
option to patch to set dates/times on files and I also did not use -j option
to make.

  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?

  When I tried to recreate problem (by doing "touch 
include/linux/console_struct.h"), all objects which use this file were
correctly rebuilt.
                                    Thanks,
                                        Petr Vandrovec
                                        vandrove@vc.cvut.cz
                                        

             reply	other threads:[~2003-01-09 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:33 Petr Vandrovec [this message]
2003-01-10 17:35 ` How build dependencies work/are supposed to work in 2.5.5x Sam Ravnborg

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=CC66A71361E@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --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 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.