linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: New btrfs-progs integration branch
Date: 06 Jun 2012 13:48:00 +0200	[thread overview]
Message-ID: <CAMlaX89CXB@helmut.hullen.de> (raw)
In-Reply-To: <20120605190921.GM15986@carfax.org.uk>

Hallo, Hugo,

Du meintest am 05.06.12:

>    The branch is fetchable with git from:

> http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
> integration-20120605

There seems to be a bug inside:

[...]

gcc -g -O0 -o btrfsck btrfsck.o ctree.o disk-io.o radix-tree.o extent- 
tree.o print-tree.o root-tree.o dir-item.o file-item.o inode-item.o  
inode-map.o crc32c.o rbtree.o extent-cache.o extent_io.o volumes.o  
utils.o btrfs-list.o btrfslabel.o repair.o  -luuid

gcc -g -O0 -o btrfs-convert ctree.o disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o dir-item.o file-item.o inode-item.o inode-map.o crc32c.o rbtree.o extent-cache.o extent_io.o volumes.o utils.o btrfs-list.o btrfslabel.o repair.o convert.o -lext2fs -lcom_err  -luuid

gcc   convert.o   -o convert
convert.o: In function `btrfs_item_key':
/tmp/btrfs-progs-unstable/ctree.h:1404: undefined reference to `read_extent_buffer'
convert.o: In function `btrfs_dir_item_key':
/tmp/btrfs-progs-unstable/ctree.h:1437: undefined reference to `read_extent_buffer'
convert.o: In function `btrfs_del_item':

[...]

Viele Gruesse!
Helmut

  reply	other threads:[~2012-06-06 12:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 19:09 New btrfs-progs integration branch Hugo Mills
2012-06-06 11:48 ` Helmut Hullen [this message]
2012-06-06 13:14   ` Hugo Mills
2012-06-06 15:03     ` Helmut Hullen
2012-06-06 15:40       ` Hugo Mills
2012-06-06 15:52         ` Helmut Hullen
2012-06-06 16:04           ` Hugo Mills
2012-06-06 16:18             ` Helmut Hullen
2012-06-06 16:26               ` Hugo Mills
2012-06-06 19:13     ` Helmut Hullen
2012-06-07  1:08 ` Jérôme Poulin
2012-06-26  8:58 ` Alex Lyakas
2012-06-26  9:58   ` Hugo Mills
2012-06-26 18:43     ` Alex Lyakas

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=CAMlaX89CXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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).