From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Perfect Gentleman <perfect007gentleman@gmail.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: f2fs-tool-1.7.0 build error
Date: Fri, 29 Jul 2016 10:22:26 -0700 [thread overview]
Message-ID: <20160729172226.GA9499@jaegeuk> (raw)
In-Reply-To: <e617e773-35c8-8eff-e7fe-0c1c798c1213@gmail.com>
Hello,
I've fixed up right away.
Thanks,
On Fri, Jul 29, 2016 at 11:22:24AM +0700, Perfect Gentleman wrote:
> >>> Source configured.
> >>> Compiling source in
> /tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999 ...
> make -j7
> make all-recursive
> make[1]: Entering directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999'
> Making all in man
> make[2]: Entering directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999/man'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999/man'
> Making all in lib
> make[2]: Entering directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999/lib'
> /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
> -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -march=native -mtune=native
> -O2 -pipe -fomit-frame-pointer -fno-stack-protector -c -o
> libf2fs_la-libf2fs.lo `test -f 'libf2fs.c' || echo './'`libf2fs.c
> /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
> -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -march=native -mtune=native
> -O2 -pipe -fomit-frame-pointer -fno-stack-protector -c -o
> libf2fs_la-libf2fs_io.lo `test -f 'libf2fs_io.c' || echo './'`libf2fs_io.c
> /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
> -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -march=native -mtune=native
> -O2 -pipe -fomit-frame-pointer -fno-stack-protector -c -o
> libf2fs_la-zbc.lo `test -f 'zbc.c' || echo './'`zbc.c
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c zbc.c -fPIC -DPIC -o
> .libs/libf2fs_la-zbc.o
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c libf2fs_io.c -fPIC -DPIC
> -o .libs/libf2fs_la-libf2fs_io.o
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c libf2fs.c -fPIC -DPIC -o
> .libs/libf2fs_la-libf2fs.o
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c libf2fs_io.c -o
> libf2fs_la-libf2fs_io.o >/dev/null 2>&1
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c zbc.c -o libf2fs_la-zbc.o
> >/dev/null 2>&1
> libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..
> -I../include -Wall -march=native -mtune=native -O2 -pipe
> -fomit-frame-pointer -fno-stack-protector -c libf2fs.c -o
> libf2fs_la-libf2fs.o >/dev/null 2>&1
> /bin/sh ../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -Wall
> -march=native -mtune=native -O2 -pipe -fomit-frame-pointer
> -fno-stack-protector -version-info 0:2:1 -Wl,-O1 -Wl,--as-needed -o
> libf2fs.la -rpath /lib64 libf2fs_la-libf2fs.lo libf2fs_la-libf2fs_io.lo
> libf2fs_la-zbc.lo
> libtool: error: AGE '1' is greater than the current interface number '0'
> libtool: error: '0:2:1' is not valid version information
> make[2]: *** [Makefile:411: libf2fs.la] Error 1
> make[2]: Leaving directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999/lib'
> make[1]: *** [Makefile:415: all-recursive] Error 1
> make[1]: Leaving directory
> '/tmp/portage/sys-fs/f2fs-tools-9999/work/f2fs-tools-9999'
> make: *** [Makefile:347: all] Error 2
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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:[~2016-07-29 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 4:22 f2fs-tool-1.7.0 build error Perfect Gentleman
2016-07-29 17:22 ` 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=20160729172226.GA9499@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=perfect007gentleman@gmail.com \
/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).