On 01/25/2013 07:09 PM, Ian Kumlien wrote:
Sometimes, when you least expect it, a static binary is what you need to
rescue your data... Or just get a good enough handle on things to make
it work again ;)
You certainly have a good point. I took q quick look on Fedora 18 and
e2fsprogs has a separate static package but xfsprogs, jfsutils, and
reiserfs-utils do not. On the other hand, those without a separate
static package may be only static.
I guess it depends how much bloat there would be with static only. For
e2fsprogs, the static package only contains the static (".a")
libraries. I believe your patch makes all of the binaries static linked.
Is this necessary? 1) Btrfs fixes a lot of stuff on-the fly. 2) If you
need to recover "standalone", rescue has btrfs.
I did a quick check and most of the btrfs binaries are less than 200K
bytes whereas the static versions are around 1.2M bytes. I know that
disk space is cheap these days but does this solve a real problem?
Gene
"make static" is a gift to you, dear user with filesystem problems!
---
Makefile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Makefile b/Makefile
index 4894903..9148d0b 100644
--- a/Makefile
+++ b/Makefile
@@ -117,4 +117,8 @@ install: $(progs) install-man
$(INSTALL) -m755 -d $(DESTDIR)$(bindir)
$(INSTALL) $(progs) $(DESTDIR)$(bindir)
+static: CFLAGS += -static
+static: LIBS += -lpthread
+static: all
+
-include .*.d
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
