From: Sam Ravnborg <sam@ravnborg.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] linux kernel conf 0.6
Date: Mon, 23 Sep 2002 21:59:49 +0200 [thread overview]
Message-ID: <20020923215949.A1310@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0209221727290.11808-100000@chaos.physics.uiowa.edu>; from kai@tp1.ruhr-uni-bochum.de on Sun, Sep 22, 2002 at 05:36:25PM -0500
On Sun, Sep 22, 2002 at 05:36:25PM -0500, Kai Germaschewski wrote:
> > > scripts/lkc/Makefile*
> > > - As kbuild does not distingush between individual objects,
> > > used for a given target, but (try to) build them all, I have
> > > found a solution where I create one Makefile for each executable.
> > > I could not see a clean way to integrate this in kbuild, and finally
> > > decided that in this special case a number of Makefiles did not
> > > hurt too much.
> >
> > Here I thought about using "ifeq ($(MAKECMDGOALS),...)" to keep them in a
> > single file. Did you try something like this?
>
> That's now handled without obvious hacks.
Applying $(sort ) to create a unique list of obj files does not solve
this issue, only hide it.
kbuild will compile all .o files originating from .c files when
building conf and mconf.
Likewise when building qconf, all .o files originating from both .c _and_
.cc files will be built.
In other words the current solution leverage on the fact that the only
problematic object files is qconf.o based on qconf.cc.
It is OK that the first "make oldconfig" - automatic or not -
needs to compile one extra .o file (mconf.o), since this is relatively fast.
PS. linux-isdn.bkbits.net/linux-2.5.kconfig has not showed up yet - mentioned
the patch you posted a diff for.
Sam
next prev parent reply other threads:[~2002-09-23 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 23:16 linux kernel conf 0.6 Roman Zippel
2002-09-20 5:10 ` [kbuild-devel] " Sam Ravnborg
2002-09-22 15:24 ` Roman Zippel
2002-09-22 22:36 ` Kai Germaschewski
2002-09-22 22:41 ` Jeff Garzik
2002-09-22 22:51 ` Kai Germaschewski
2002-09-22 22:53 ` Jeff Garzik
2002-09-22 23:03 ` Kai Germaschewski
2002-09-23 1:48 ` Jeff Garzik
2002-09-22 23:07 ` Roman Zippel
2002-09-22 23:19 ` Kai Germaschewski
2002-09-22 23:30 ` Roman Zippel
2002-09-23 1:50 ` Jeff Garzik
2002-09-23 19:59 ` Sam Ravnborg [this message]
2002-10-03 11:17 ` Roman Zippel
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=20020923215949.A1310@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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