From: Sam Ravnborg <sam@ravnborg.org>
To: Michael Still <mikal@stillhq.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Makefile dependancies: scripts depending on configured kernel?
Date: Mon, 22 Mar 2004 06:56:17 +0100 [thread overview]
Message-ID: <20040322055617.GA2250@mars.ravnborg.org> (raw)
In-Reply-To: <405E1427.6080309@stillhq.com>
On Mon, Mar 22, 2004 at 09:16:07AM +1100, Michael Still wrote:
>
> Hey,
>
> the top level Makefile specifies that the scripts depend on the kernel
> being configured before the scripts can be built:
>
> scripts: scripts_basic include/config/MARKER
> $(Q)$(MAKE) $(build)=$(@)
>
> I think that this is probably a problem, because it means people can't
> build any of the documentation targets without having configured the kernel.
The dependency for docs is (now) wrong.
It should be:
# Documentation targets
# ---------------------------------------------------------------------------
%docs: scripts_basic FORCE
$(Q)$(MAKE) $(build)=Documentation/DocBook $@
docproc is the only binary used by Documentation/Docbook, and it is already
placed in scripts_basic.
Trivial - so I will include this in some other kbuild patch
I'm preparing.
> Do any of the scripts actually depend on a configured kernel to build?
Yes, several of the ninaries do so. Among others empty.o.
> How can I verify that none of them need a configured kernel? Commenting
> out the dependancy didn't break anything.
Test a bit more, and you will see they are indeed needed.
Note, some archs other than i386 have a bit different requirements
because thay do not use an asm-offsett.h file.
Sam
next prev parent reply other threads:[~2004-03-22 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 22:16 Michael Still
2004-03-22 5:56 ` Sam Ravnborg [this message]
2004-03-22 9:14 ` Michael Still
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=20040322055617.GA2250@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikal@stillhq.com \
/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®