From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, Anand Jain <anand.jain@oracle.com>
Subject: [PATCH 1/3] btrfs-progs: fix make install failure
Date: Thu, 19 May 2016 13:13:12 +0800 [thread overview]
Message-ID: <1463634794-591-2-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1463634794-591-1-git-send-email-anand.jain@oracle.com>
/usr/bin/install -c -m644 -d 64-btrfs-dm.rules /usr/lib/udev/rules.d
/usr/bin/install: cannot create directory ‘64-btrfs-dm.rules’: File exists
Makefile:400: recipe for target 'install' failed
make: *** [install] Error 1
fixes: btrfs-progs: udev: add rules for dm devices
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
Makefile.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile.in b/Makefile.in
index 47e73c9fbc4e..238dd59badaf 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -408,7 +408,7 @@ install: $(libs) $(progs_install) $(INSTALLDIRS)
$(INSTALL) -m755 -d $(DESTDIR)$(incdir)
$(INSTALL) -m644 $(headers) $(DESTDIR)$(incdir)
ifneq ($(udevdir),)
- $(INSTALL) -m644 -d $(udev_rules) $(DESTDIR)$(udevruledir)
+ $(INSTALL) -m644 $(udev_rules) $(DESTDIR)$(udevruledir)
endif
install-static: $(progs_static) $(INSTALLDIRS)
--
2.7.0
next prev parent reply other threads:[~2016-05-19 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 5:13 [PATCH 0/3] btrfs-progs: fixes on top of latest integration branch Anand Jain
2016-05-19 5:13 ` Anand Jain [this message]
2016-05-19 12:00 ` [PATCH 1/3] btrfs-progs: fix make install failure David Sterba
2016-05-19 5:13 ` [PATCH 2/3] btrfs-progs: add clean-all to the usage Anand Jain
2016-05-19 5:13 ` [PATCH 3/3] btrfs-progs: clean up commands.h Anand Jain
2016-05-19 12:07 ` [PATCH 0/3] btrfs-progs: fixes on top of latest integration branch David Sterba
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=1463634794-591-2-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).