[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+8MBb+Kk=G5GQbSdbjXqFmw+GCON6jLZABCAGuL+bNDC+dLgA@mail.gmail.com>
Date: Wed, 20 Jun 2012 16:12:51 -0700
From: Tony Luck <tony.luck@...il.com>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Anders Larsen <al@...rsen.net>,
Alasdair Kergon <agk@...hat.com>, dm-devel@...hat.com,
linux-fsdevel@...r.kernel.org,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org, Mark Fasheh <mfasheh@...e.com>,
Joel Becker <jlbec@...lplan.org>, ocfs2-devel@....oracle.com,
Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org,
Andreas Dilger <adilger.kernel@...ger.ca>,
"Theodore Ts'o" <tytso@....edu>, Matthew Wilcox <matthew@....cx>
Subject: Re: [PATCH v3 1/9] string: introduce memweight
On Fri, Jun 8, 2012 at 5:50 PM, Akinobu Mita <akinobu.mita@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists