From: fche@redhat.com (Frank Ch. Eigler)
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: systemtap@sources.redhat.com
Subject: Re: Latest systemtap fails when used with latest Linux kernel
Date: Tue, 06 Jan 2009 18:39:00 -0000 [thread overview]
Message-ID: <y0m8wpojn3k.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <E1LK6di-00037H-Hl@closure.thunk.org> (Theodore Ts'o's message of "Tue, 06 Jan 2009 02:46:14 -0500")
"Theodore Ts'o" <tytso@mit.edu> writes:
> Using the latest Systemtap (commit be21f2db) compiling a 2.6.28-git7
> kernel, I get this failure....
> [...]
Initial results (using an O=DIR x86_64 build) indicate that the kbuild
machinery was broken with respect to the include2/ symlink directory
in the build tree. It was not updated when commit
bb8985586b7a906e116db835c64773b7a7d51663 moved a bunch of files from
include/asm/x86/ to arch/include/asm/.
- FChE
next prev parent reply other threads:[~2009-01-06 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 7:46 Theodore Ts'o
2009-01-06 8:50 ` Srikar Dronamraju
2009-01-06 17:49 ` Frank Ch. Eigler
2009-01-06 20:45 ` Masami Hiramatsu
2009-01-06 23:09 ` Masami Hiramatsu
2009-01-06 18:39 ` Frank Ch. Eigler [this message]
2009-01-06 20:30 ` David Smith
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=y0m8wpojn3k.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).