From: Brendan J Simon <brendan.simon@bigpond.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: touch commands in Makefiles
Date: Fri, 25 Jan 2002 16:54:39 +1100 [thread overview]
Message-ID: <3C50F31F.1090302@bigpond.com> (raw)
Why are header file touched in Makefiles ?
The reason I ask is that I am using a configuration management system to
maintain the linux kernel. It "checks out" all source files read-only
(actuall it uses symbolic links to a baseline directory which is
read-only). You then tell it which files you intend to modify and it
will check those files out as read-write to the local sandbox.
When trying to do a "make zImage" some of the header files (eg.
include/linux/types.h) are being touched by a dependency rule. The
build is failing as the files are readonly and can't be touched. I
don't understand why the header files need to be touched. Surely the
"make dep" should only generate rules to recompile .c files.
Thanks for any help explaining why header files need to be touched.
Regards,
Brendan Simon.
next reply other threads:[~2002-01-25 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 5:54 Brendan J Simon [this message]
2002-01-26 10:38 ` touch commands in Makefiles Keith Owens
2002-01-28 8:17 ` Marian Jancar
2002-01-28 8:20 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 1:29 Peter Samuelson
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=3C50F31F.1090302@bigpond.com \
--to=brendan.simon@bigpond.com \
--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