[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH v3 1/9] string: introduce memweight
- From: Tony Luck <tony luck gmail com>
- To: Akinobu Mita <akinobu mita gmail com>
- Cc: Theodore Ts'o <tytso mit edu>, linux-ext4 vger kernel org, Jan Kara <jack suse cz>, Matthew Wilcox <matthew wil cx>, Mark Fasheh <mfasheh suse com>, Anders Larsen <al alarsen net>, linux-kernel vger kernel org, dm-devel redhat com, ocfs2-devel oss oracle com, Laurent Pinchart <laurent pinchart ideasonboard com>, linux-fsdevel vger kernel org, Andreas Dilger <adilger kernel dilger ca>, akpm linux-foundation org, Joel Becker <jlbec evilplan org>, Alasdair Kergon <agk redhat com>, linux-media vger kernel org
- Subject: Re: [dm-devel] [PATCH v3 1/9] string: introduce memweight
- Date: Wed, 20 Jun 2012 16:12:51 -0700
On Fri, Jun 8, 2012 at 5:50 PM, Akinobu Mita <akinobu mita gmail com> wrote:
> lib/string.c | 36 ++++++++++++++++++++++++++++++++++++
Is lib/string.c the right place for this? I get a build error on the
ia64 sim_defconfig:
LD arch/ia64/hp/sim/boot/bootloader
It fails because it pulls in lib/lib.a(string.o) to get some
innocuous function like strcpy() ... but it also gets
given memweight() which relies on __bitmap_weight()
which it doesn't have, because it doesn't include lib/built-in.o
(which is where bitmap.o, the definer of __bitmap_weight(), has
been linked).
Moving memweight() to lib/bitmap.c fixes the problem. But it
isn't really clear that it belongs there either. Perhaps it should
be its own file lib/memweight.c that gets included in lib/lib.a?
-Tony
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]