linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Becker <floyd.net@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: build error btrfs-progs 4.8.1
Date: Fri, 21 Oct 2016 23:30:40 +0200	[thread overview]
Message-ID: <CAEtw4r3O3qZd0qT1_9T3eu37PLgtBqaKbz8LtmKAhQSRu0RaEw@mail.gmail.com> (raw)
In-Reply-To: <CAEtw4r3fGWmR_reiYh7azaVnTsv=W9CV0-GNKWTju8wP9BfWFQ@mail.gmail.com>

Generate build-system by:
   aclocal:    aclocal (GNU automake) 1.15
   autoconf:   autoconf (GNU Autoconf) 2.69
   autoheader: autoheader (GNU Autoconf) 2.69
   automake:   automake (GNU automake) 1.15

Now type './configure' and 'make' to compile.

checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking whether byte ordering is bigendian... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ar... ar
checking for rm... /bin/rm
checking for rmdir... /bin/rmdir
checking for openat... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking for backtrace... yes
checking for backtrace_symbols_fd... yes
checking for asciidoc... /usr/bin/asciidoc
checking for xmlto... /usr/bin/xmlto
checking for gzip... /bin/gzip
checking for mv... /bin/mv
checking for a sed that does not truncate output... /bin/sed
checking for EXT2FS... yes
checking for COM_ERR... yes
checking for FIEMAP_EXTENT_SHARED defined in linux/fiemap.h... yes
checking for BLKID... yes
checking for UUID... yes
checking for ZLIB... yes
checking for lzo_version in -llzo2... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating Documentation/Makefile
config.status: creating version.h
config.status: creating config.h
config.status: config.h is unchanged

btrfs-progs v4.8.1

prefix:            /usr/local
exec prefix:       ${prefix}

bindir:            ${exec_prefix}/bin
libdir:            ${exec_prefix}/lib
includedir:        ${prefix}/include

compiler:          gcc
cflags:            -g -O1 -Wall -D_FORTIFY_SOURCE=2
ldflags:

documentation:     yes
backtrace support: yes
btrfs-convert:     yes (ext2)

Type 'make' to compile.

make: *** Keine Regel vorhanden, um das Ziel "list.h",
   benötigt von "ctree.o", zu erstellen.  Schluss.

2016-10-21 23:23 GMT+02:00 Peter Becker <floyd.net@gmail.com>:
> $ uname -r
> 4.8.3-040803-generic
>
> $ git remote -v
> origin git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
> (fetch)
> origin git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
> (push)
>
> $ git pull
> Already up-to-date.
>
> $ ./autogen.sh
> ...
> $ ./configure
> ...
> $ make
> ...
> make: *** Keine Regel vorhanden, um das Ziel "list.h",
>    benötigt von "ctree.o", zu erstellen.  Schluss.

  reply	other threads:[~2016-10-21 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 21:23 build error btrfs-progs 4.8.1 Peter Becker
2016-10-21 21:30 ` Peter Becker [this message]
2016-10-22 19:32   ` Peter Becker
2016-10-24  1:08     ` Qu Wenruo

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=CAEtw4r3O3qZd0qT1_9T3eu37PLgtBqaKbz8LtmKAhQSRu0RaEw@mail.gmail.com \
    --to=floyd.net@gmail.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).