From: Changman Lee <cm224.lee@samsung.com>
To: folkert <folkert@vanheusden.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] fails to build
Date: Mon, 08 Jul 2013 18:46:11 +0900 [thread overview]
Message-ID: <1373276771.14296.30.camel@lcm> (raw)
In-Reply-To: <20130706145001.GB19245@belle.intranet.vanheusden.com>
I'm sorry to fail compiling.
Frankly speaking, I don't know the solution about it. I guess it's due
to version of libtoolize.
I'm using 'libtoolize (GNU libtool) 2.4.2'.
I'll think about the *.deb of f2fs-tools a little more.
Thanks.
On 토, 2013-07-06 at 16:50 +0200, folkert wrote:
> Hi,
>
> f2fs-tools fails to build:
>
> root@vnvnation:/usr/src/f2fs-tools# autoreconf --install
> configure.ac:36: installing `build-aux/install-sh'
> configure.ac:36: installing `build-aux/missing'
> fsck/Makefile.am: installing `build-aux/depcomp'
> lib/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined
> lib/Makefile.am:3: The usual way to define `LIBTOOL' is to add `LT_INIT'
> lib/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again.
> lib/Makefile.am:3: If `LT_INIT' is in `configure.ac', make sure
> lib/Makefile.am:3: its definition is in aclocal's search path.
> autoreconf: automake failed with exit status: 1
>
> I tried adding LT_INIT to configure.ac but that did not help.
>
> Any ideas?
>
> Also: please consider publishing debian packages.
>
>
> Folkert van Heusden
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
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-07-08 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 14:50 [f2fs-dev] fails to build folkert
2013-07-08 9:46 ` Changman Lee [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=1373276771.14296.30.camel@lcm \
--to=cm224.lee@samsung.com \
--cc=folkert@vanheusden.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.