From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: "Sérgio Benjamim" <sergio_br2@ig.com.br>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: libtool package is missing from README
Date: Mon, 16 Dec 2013 12:35:16 +0900 [thread overview]
Message-ID: <1387164916.2101.208.camel@kjgkr> (raw)
In-Reply-To: <52AE3B55.301@ig.com.br>
Hi,
Thank you for the suggestion.
I made a patch and then applied it to the git tree.
Thanks,
From 11d187cdfa2dcf504aa25b5a1aab4228f19f22ff Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Date: Mon, 16 Dec 2013 12:32:37 +0900
Subject: [PATCH] README: add libtool guide
The f2fs-tools needs libtool package to compile sources.
Suggested-by: Sérgio Benjamim <sergio_br2@ig.com.br>
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
---
README | 1 +
1 file changed, 1 insertion(+)
diff --git a/README b/README
index bf374fb..222cbc3 100644
--- a/README
+++ b/README
@@ -11,6 +11,7 @@ Your should install the following packages.
- libuuid-devel or uuid-dev
- pkg-config
- autoconf
+ - libtool
Initial compilation
-------------------
--
1.8.4.474.g128a96c
--
Jaegeuk Kim
Samsung
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2013-12-16 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 23:29 libtool package is missing from README Sérgio Benjamim
2013-12-16 3:35 ` Jaegeuk Kim [this message]
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=1387164916.2101.208.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=sergio_br2@ig.com.br \
/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).