From: Randy Dunlap <randy.dunlap@oracle.com>
To: Luciano Rocha <strange@nsk.no-ip.org>
Cc: linux-kernel@vger.kernel.org, akpm <akpm@linux-foundation.org>,
torvalds <torvalds@linux-foundation.org>
Subject: [patch available] Re: lguest compilation problem in 2.6.23-rc9
Date: Fri, 5 Oct 2007 09:18:09 -0700 [thread overview]
Message-ID: <20071005091809.d11f8003.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20071005152147.GA8160@bit.office.eurotux.com>
On Fri, 5 Oct 2007 16:21:47 +0100 Luciano Rocha wrote:
>
> $ git describe
> v2.6.23-rc9
>
> $ make
> ...
> BUILD arch/i386/boot/bzImage
> Root device is (254, 3)
> Setup is 11496 bytes (padded to 11776 bytes).
> System is 1233 kB
> Kernel: arch/i386/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST 282 modules
> ERROR: "kasprintf" [drivers/lguest/lg.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> Latest Linus' kernel tree:
> $ git describe
> v2.6.23-rc9-41-g804b3f9
> $ make oldconfig
> ...
> $ make
> BUILD arch/i386/boot/bzImage
> Root device is (254, 3)
> Setup is 11496 bytes (padded to 11776 bytes).
> System is 1234 kB
> Kernel: arch/i386/boot/bzImage is ready (#2)
> Building modules, stage 2.
> MODPOST 282 modules
> ERROR: "kasprintf" [drivers/lguest/lg.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> Config follows.
Fixed by
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/broken-out/move-kasprintfo-to-obj-y.patch
Need to merge now?
---
~Randy
next prev parent reply other threads:[~2007-10-05 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 15:21 Luciano Rocha
2007-10-05 16:18 ` Randy Dunlap [this message]
2007-10-05 17:40 ` [patch available] " Andrew Morton
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=20071005091809.d11f8003.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=strange@nsk.no-ip.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome