linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: uti-linux-ng libblkid
Date: Mon, 9 Mar 2009 11:42:54 +0100	[thread overview]
Message-ID: <20090309104254.GC3278@nb.net.home> (raw)
In-Reply-To: <20090309010833.GE5578@mit.edu>

On Sun, Mar 08, 2009 at 09:08:33PM -0400, Theodore Tso wrote:
> On Mon, Feb 23, 2009 at 06:38:51PM +0100, Karel Zak wrote:
> > Hi Ted,
> > 
> > here are two patches that allow to link utils from e2fsprogs with
> > external libblkid (e.g. the version from util-linux-ng).
> 
> Thanks, I'm starting to play with the builtin fsprobe libraries in
> util-linux-ng right now.  Some quick issues I've found right off the
> bat.  Automake is returning these errors:
> 
> configure.ac:8: required file `config/missing' not found
> configure.ac:8:   `automake --add-missing' can install `missing'

 Did you run ./autogen.sh script? (It outputs versions of all relevant
 autotoos, this output is useful for debuging.)

 Maybe I can prepare a .tar.gz snapshot with generated build-system.

> Also, the configure --help for --with-fsprobe is currently:
> 
>   --with-fsprobe          library to guess filesystems
>                           (builtin|blkid|volume_id), default is blkid
> 
> It would probably clearer if it read:
> 
>   --with-fsprobe=LIB      library to guess filesystems
>                           LIB should be builtin|blkid|volume_id,
> 			  default is blkid

 Good point.

> Also note there have been a couple of blkid fixes that have been made
> to e2fsprogs git tree, I'll look into getting those pushed to you.

 No problem, I'll pull from your tree. I think the missing fixes are
 the latests patches from February only. All older fixes should be
 already in my tree.

 Thanks for your feedback.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>

  reply	other threads:[~2009-03-09 10:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 17:38 uti-linux-ng libblkid Karel Zak
2009-02-23 17:38 ` [PATCH] blkid: add --disable-libblkid to build with external libblkid Karel Zak
2009-02-24  8:44   ` [PATCH] blkid: add --disable-libblkid (v2) Karel Zak
2009-03-24 12:11     ` Scott James Remnant
2009-04-16 10:22       ` Karel Zak
2009-04-17 13:36         ` Kay Sievers
2009-04-17 13:48         ` Scott James Remnant
2009-04-22 13:33           ` Theodore Tso
2009-04-22 13:42             ` Scott James Remnant
2009-04-22 13:49               ` Theodore Tso
2009-04-22 14:07                 ` Scott James Remnant
2009-04-29 17:22                 ` Scott James Remnant
2009-04-29 20:54                   ` Theodore Tso
2009-05-05 11:30                     ` Scott James Remnant
2009-04-27  9:21             ` Karel Zak
2009-04-28 20:36               ` Karel Zak
2009-04-29 13:59             ` Scott James Remnant
2009-04-29 17:17               ` Theodore Tso
2009-04-29 20:23         ` Theodore Tso
2009-04-30  8:28           ` Karel Zak
2009-02-23 17:38 ` [PATCH] tune2fs: make findfs code optional Karel Zak
2009-03-09  1:08 ` uti-linux-ng libblkid Theodore Tso
2009-03-09 10:42   ` Karel Zak [this message]
2009-03-09 11:45   ` Karel Zak
2009-03-18 19:28   ` Karel Zak

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=20090309104254.GC3278@nb.net.home \
    --to=kzak@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).