LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for January 18 (__modver_version_show)
Date: Wed, 19 Jan 2011 16:09:51 +1100 [thread overview]
Message-ID: <20110119160951.2a14d0a0.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110118091749.ac5823df.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi Randy,
On Tue, 18 Jan 2011 09:17:49 -0800 Randy Dunlap <randy.dunlap@oracle.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?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-01-19 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 1:21 linux-next: Tree for January 18 Stephen Rothwell
2011-01-18 17:17 ` linux-next: Tree for January 18 (__modver_version_show) Randy Dunlap
2011-01-19 5:09 ` Stephen Rothwell [this message]
2011-01-19 16:10 ` Randy Dunlap
2011-01-19 16:12 ` Randy Dunlap
2011-01-19 22:18 ` Rusty Russell
2011-01-20 0:38 ` Dmitry Torokhov
2011-01-20 0:59 ` Randy Dunlap
2011-01-20 1:12 ` Dmitry Torokhov
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=20110119160951.2a14d0a0.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
--subject='Re: linux-next: Tree for January 18 (__modver_version_show)' \
/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
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).