From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: vpath broken in 2.5.41
Date: Tue, 08 Oct 2002 20:09:03 +1000 [thread overview]
Message-ID: <29031.1034071743@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 07 Oct 2002 20:39:46 EST." <Pine.LNX.4.44.0210072037520.32256-100000@chaos.physics.uiowa.edu>
On Mon, 7 Oct 2002 20:39:46 -0500 (CDT),
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
>On Tue, 8 Oct 2002, John Levon wrote:
>> I see vpath seems to have become broken in 2.5.41 build.
>> How now can I build the oprofile.o target from two directories ?
>
>I see in the patch you mailed later that you got it figured out already,
>using a relative path.
>And yeah, it's not particularly beautiful. But I do not see any nice and
>easy way, either.
This is one of the problems that kbuild 2.5 was designed to handle, to
cope with modules built from code in multiple directories. I support
what the developer wants to do, not restrict the developer to what the
kernel build can handle.
Pity that Linus thinks that there are no kbuild problems that require
kbuild 2.5 ...
next prev parent reply other threads:[~2002-10-08 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 23:28 vpath broken in 2.5.41 John Levon
2002-10-08 1:39 ` Kai Germaschewski
2002-10-08 1:53 ` John Levon
2002-10-08 10:09 ` Keith Owens [this message]
2002-10-08 14:35 ` Kai Germaschewski
2002-10-08 22:31 ` Keith Owens
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=29031.1034071743@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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