public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Cc: kai@tp1.ruhr-uni-bochum.de
Subject: Re: vpath broken in 2.5.41
Date: Tue, 8 Oct 2002 02:53:59 +0100	[thread overview]
Message-ID: <20021008015359.GA38838@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210072037520.32256-100000@chaos.physics.uiowa.edu>

On Mon, Oct 07, 2002 at 08:39:46PM -0500, Kai Germaschewski wrote:

> > 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.

OK. If you say that the vpath support is troublesome, I will believe
you :)

> What would help a lot, of course, would be to split this 
> into two modules, one generic one, one arch-specific one. Have you 
> considered doing that?

I think I said to you before that implementing a runtime solution to a
build time problem is a little bizarre IMHO. I would *much* rather have
4 lines of slightly icky Makefile than complicate *any* runtime code.

I suppose it would not be much more complicated than a request_module()
inside oprofile_init(), but it's still more code for next-to-zero
benefit ...

regards
john
-- 
"I will eat a rubber tire to the music of The Flight of the Bumblebee"

  reply	other threads:[~2002-10-08  1:48 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 [this message]
2002-10-08 10:09   ` Keith Owens
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=20021008015359.GA38838@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --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