From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH] btrfs-progs: fix btrfs-fragments build
Date: Fri, 30 May 2014 11:29:19 -0500 [thread overview]
Message-ID: <5388B1DF.9030307@redhat.com> (raw)
When I made all the btrfs-foo.c targets generic, I somehow
managed to break the libs definition for btrfs-fragments by
dropping the "s" off the end.
Fix that, although apparently nobody is building this tool. :)
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
As an aside, since it's not built by default, it seems at-risk
for this kind of bitrot...
diff --git a/Makefile b/Makefile
index 76565e8..037a1c4 100644
--- a/Makefile
+++ b/Makefile
@@ -54,7 +54,7 @@ progs = mkfs.btrfs btrfs-debug-tree btrfsck \
# specify btrfs_foo_libs = <list of libs>; see $($(subst...)) rules below
btrfs_convert_libs = -lext2fs -lcom_err
btrfs_image_libs = -lpthread
-btrfs_fragment_libs = -lgd -lpng -ljpeg -lfreetype
+btrfs_fragments_libs = -lgd -lpng -ljpeg -lfreetype
SUBDIRS =
BUILDDIRS = $(patsubst %,build-%,$(SUBDIRS)) build-Documentation
reply other threads:[~2014-05-30 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5388B1DF.9030307@redhat.com \
--to=sandeen@redhat.com \
--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).