From: John Levon <levon@movementarian.org>
To: kai@tp1.ruhr-uni-bochum.de
Cc: linux-kernel@vger.kernel.org
Subject: vpath broken in 2.5.41
Date: Tue, 8 Oct 2002 00:28:52 +0100 [thread overview]
Message-ID: <20021007232852.GA35308@compsoc.man.ac.uk> (raw)
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 ?
Namely,
arch/i386/oprofile/Makefile:
vpath %.c = . $(TOPDIR)/drivers/oprofile
obj-$(CONFIG_OPROFILE) += oprofile.o
DRIVER_OBJS = \
oprof.o cpu_buffer.o buffer_sync.o \
event_buffer.o oprofile_files.o \
oprofilefs.o oprofile_stats.o
oprofile-objs := $(DRIVER_OBJS) init.o timer_int.o
ifdef CONFIG_X86_LOCAL_APIC
oprofile-objs += nmi_int.o op_model_athlon.o op_model_ppro.o
endif
include $(TOPDIR)/Rules.make
with the DRIVER_OBJS sources in drivers/oprofile/
Since this was intentional, I assume I have to move my arch-dependent
parts back into drivers/ Kai ?
thanks
john
--
"I will eat a rubber tire to the music of The Flight of the Bumblebee"
next reply other threads:[~2002-10-07 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 23:28 John Levon [this message]
2002-10-08 1:39 ` vpath broken in 2.5.41 Kai Germaschewski
2002-10-08 1:53 ` John Levon
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=20021007232852.GA35308@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