linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: Minimal configuration for e2fsprogs
Date: Mon, 30 Jul 2012 17:45:32 -0400	[thread overview]
Message-ID: <20120730214531.GE10343@thunk.org> (raw)
In-Reply-To: <20120628024356.GB17989@thor.bakeyournoodle.com>

On Thu, Jun 28, 2012 at 12:43:56PM +1000, Tony Breeds wrote:
> 
> Okay so I think you want somethign like:

Yep!

> What I did was remove dblist.o from my libext2fs.a and I now get:
> /home/tony/src/e2fsprogs/../e2fsprogs-root/lib/libext2fs.a(gen_bitmap64.o): In function `ext2fs_alloc_generic_bmap':
> /home/tony/src/e2fsprogs-build/lib/ext2fs/../../../e2fsprogs/lib/ext2fs/gen_bitmap64.c:112: undefined reference to `ext2fs_get_num_dirs'
> 
> So it looks like dblist.o is being pulled in for ext2fs_get_num_dirs()
> in that case a EXT2FS_BMAP64_AUTODIR bmap type has been asked for.
> 
> How would you feel about moving ext2fs_get_num_dirs from dblist.c to
> blknum.c?

Sure, no problem.

Take a look at this set of patches (see attached).  With this and the
set of ext2fs functions that I understand yaboot is using, I think it
solves the concern that you have.  This will be in the next branch of
the e2fsprogs.

Regards,

					- Ted

  reply	other threads:[~2012-07-30 21:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15  4:24 Minimal configuration for e2fsprogs Tony Breeds
2012-06-16  0:08 ` Ted Ts'o
2012-06-18  5:58   ` Tony Breeds
2012-06-18 17:12     ` Ted Ts'o
2012-06-19  5:48       ` Tony Breeds
2012-06-19  6:01         ` Andreas Dilger
2012-06-19 13:56           ` Ted Ts'o
2012-06-20  5:26             ` Tony Breeds
2012-06-20  5:33               ` Tony Breeds
2012-06-20 14:14               ` Andreas Dilger
2012-06-20  4:45           ` Tony Breeds
2012-06-26  2:10       ` Tony Breeds
2012-06-26  2:33         ` Theodore Ts'o
2012-06-26  2:47           ` Tony Breeds
2012-06-27 11:21 ` Tony Breeds
2012-06-27 12:54   ` Theodore Ts'o
2012-06-28  2:43     ` Tony Breeds
2012-07-30 21:45       ` Theodore Ts'o [this message]
2012-07-31  5:21         ` Tony Breeds
2012-07-31 19:57           ` Theodore Ts'o
2012-08-01  5:42             ` Tony Breeds
2012-07-30 21:47       ` [PATCH 1/7] e2fsck: add SIGABRT to list of signals processed by sigcatcher Theodore Ts'o
2012-07-30 21:47         ` [PATCH 2/7] libext2fs: use abort() instead of perror()/exit() Theodore Ts'o
2012-07-31 18:34           ` Andreas Dilger
2012-07-31 20:04             ` Theodore Ts'o
2012-07-30 21:47         ` [PATCH 3/7] libext2fs: use strcpy()/strcat() instead of sprintf() in bmap functions Theodore Ts'o
2012-07-30 21:47         ` [PATCH 4/7] libext2fs: move ext2fs_get_num_dirs to its own file Theodore Ts'o
2012-07-30 21:47         ` [PATCH 5/7] libext2fs: call numeric_progress functions through a operations struct Theodore Ts'o
2012-07-30 21:47         ` [PATCH 6/7] libext2fs: remove debugging printf from ext2fs_group_desc_csum Theodore Ts'o
2012-07-30 21:47         ` [PATCH 7/7] libext2fs: enforce the block group descriptor size in ext2fs_open() Theodore Ts'o
2012-07-31 18:38           ` Andreas Dilger
2012-07-31 20:09             ` Theodore Ts'o
2012-08-01 20:45               ` Andreas Dilger
2012-08-03  0:00                 ` Theodore Ts'o

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=20120730214531.GE10343@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@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).