From: Mike Frysinger <vapier@gentoo.org>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] ubi-utils: tweak vpath handling
Date: Tue, 31 Mar 2009 00:09:40 -0400 [thread overview]
Message-ID: <1238472580-4762-1-git-send-email-vapier@gentoo.org> (raw)
Building out of tree currently fails with ubi-utils because make gets
confused and can't figure out the vpathed .c files. Using VPATH rather
than vpath seems to work around it.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
ubi-utils/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/ubi-utils/Makefile b/ubi-utils/Makefile
index 020fe09..dcff7e3 100644
--- a/ubi-utils/Makefile
+++ b/ubi-utils/Makefile
@@ -13,7 +13,7 @@ LIBS = libubi libmtd libubigen libiniparser libscan
TARGETS = ubiupdatevol ubimkvol ubirmvol ubicrc32 ubinfo ubiattach \
ubidetach ubinize ubiformat ubirename
-vpath %.c src
+VPATH = src
include ../common.mk
--
1.6.2
next reply other threads:[~2009-03-31 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 4:09 Mike Frysinger [this message]
2009-03-31 6:25 ` [PATCH] ubi-utils: tweak vpath handling Artem Bityutskiy
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=1238472580-4762-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-mtd@lists.infradead.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