[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D370D63.5070503@oracle.com>
Date: Wed, 19 Jan 2011 08:12:19 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Rusty Russell <rusty@...tcorp.com.au>, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for January 18 (__modver_version_show)
On 01/19/11 08:10, Randy Dunlap wrote:
> On 01/18/11 21:09, Stephen Rothwell wrote:
>> Hi Randy,
>>
>> On Tue, 18 Jan 2011 09:17:49 -0800 Randy Dunlap <randy.dunlap@...cle.com> wrote:
>>>
>>> I'm seeing this on several builds (i386 and x86_64):
>>>
>>> lib/built-in.o:(__modver+0x8): undefined reference to `__modver_version_show'
>>> lib/built-in.o:(__modver+0x2c): undefined reference to `__modver_version_show'
>>>
>>> It looks like the compiler or linker is dropping that function from the
>>> build since it cannot see any references to it...
>>> At least __modver_version_show is not in the kernel/params.o file.
>>
>> Do these builds have CONFIG_SYSFS set?
>>
>
> Yes, they all do (50 random builds have CONFIG_SYSFS=y).
Gawd, what bad grepping this morning.
You hit the nail. They do not have SYSFS enabled.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists