From: Matt Mackall <mpm@selenic.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: jdike@addtoit.com, blaisorblade@yahoo.it, clameter@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slob: fix linking for user mode linux
Date: Mon, 11 Feb 2008 16:39:29 -0600 [thread overview]
Message-ID: <1202769569.12383.49.camel@cinder.waste.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802120032160.27876@sbz-30.cs.Helsinki.FI>
On Tue, 2008-02-12 at 00:32 +0200, Pekka J Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> UML has some header magic that expects a non-inline __kmalloc() function to be
> available. Fixes the following link time errors:
>
> arch/um/drivers/built-in.o: In function `kmalloc':
> /home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: undefined reference to `__kmalloc'
> /home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: undefined reference to `__kmalloc'
> /home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: undefined reference to `__kmalloc'
> /home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: undefined reference to `__kmalloc'
> /home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: undefined reference to `__kmalloc'
> arch/um/drivers/built-in.o:/home/penberg/linux-2.6/arch/um/include/um_malloc.h:14: more undefined references to `__kmalloc' follow
Can someone explain why the magic is needed (and preferably capture it
in a comment somewhere sensible)? I took a peek at this and have no idea
what's going on.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2008-02-11 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 22:32 Pekka J Enberg
2008-02-11 22:39 ` Matt Mackall [this message]
2008-02-11 22:44 ` Christoph Lameter
2008-02-11 23:32 ` Jeff Dike
2008-02-12 6:23 ` Pekka Enberg
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=1202769569.12383.49.camel@cinder.waste.org \
--to=mpm@selenic.com \
--cc=blaisorblade@yahoo.it \
--cc=clameter@sgi.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®