From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kmemtrace: kbuild failed to make the new header symlink...
Date: Mon, 19 Jan 2009 18:59:26 +0200 [thread overview]
Message-ID: <20090119165926.GA5287@localhost> (raw)
In-Reply-To: <20090119164029.GB19302@ghostprotocols.net>
On Mon, Jan 19, 2009 at 02:40:29PM -0200, Arnaldo Carvalho de Melo wrote:
> Sam,
>
> I just did a git pull on linux-2.6-tip, then, on a build
> directory (make O=../build/blkftrace/) with a previous build a tree
> cloned from Linus I got stuck with the messages below.
>
> I could only get this to work after a make mrproper, thought I
> could mention this so that perhaps this can get detected and time be
> saved somehow.
>
> CC arch/x86/mm/fault.o
> /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:38:27: error: asm/kmemcheck.h: No such file or directory
> /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c: In function ???do_page_fault???:
> /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:614: error: implicit declaration of function ???kmemcheck_active???
> /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:615: error: implicit declaration of function ???kmemcheck_hide???
> /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:644: error: implicit declaration of function ???kmemcheck_fault???
Hi,
This looks like a kmemcheck, not kmemtrace, fault. Heh, but we already
have 3 things with similar names: kmemcheck, kmemtrace and kmemleak. :)
Cheers,
Eduard
next prev parent reply other threads:[~2009-01-19 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 16:40 kmemtrace: kbuild failed to make the new header symlink Arnaldo Carvalho de Melo
2009-01-19 16:59 ` Eduard - Gabriel Munteanu [this message]
2009-01-19 17:09 ` Arnaldo Carvalho de Melo
2009-01-19 18:28 ` Sam Ravnborg
2009-01-19 23:29 ` Ingo Molnar
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=20090119165926.GA5287@localhost \
--to=eduard.munteanu@linux360.ro \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.