From: Theodore Tso <tytso@mit.edu>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UML build failure in 2.6.27-rc3
Date: Mon, 25 Aug 2008 19:30:20 -0400 [thread overview]
Message-ID: <20080825233020.GD9454@mit.edu> (raw)
In-Reply-To: <20080825220406.GC12626@c2.user-mode-linux.org>
On Mon, Aug 25, 2008 at 06:04:06PM -0400, Jeff Dike wrote:
> Are you sure you have a consistent tree? I see no declaration of
> send_sigtrap in ptrace-generic.h. There is one in asm-x86/ptrace.h
> but it's not at line 51.
Now I see what happened. I did have a consistent tree, but I was
doing a build via "make ARCH=um O=/usr/projects/linux/uml" --- and I
had previously built a UML tree from another source tree without doing
a "make mrproper", so /usr/projects/linux/uml/include2/asm was a
symlink to another kernel tree's include/asm directory.
It might be nice if kbuild caught the inconsistency, but this was my
bad.
- Ted
prev parent reply other threads:[~2008-08-25 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 15:19 UML build failure in 2.6.27-rc3 Theodore Ts'o
2008-08-21 15:45 ` Geert Uytterhoeven
2008-08-25 22:04 ` Jeff Dike
2008-08-25 23:30 ` Theodore Tso [this message]
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=20080825233020.GD9454@mit.edu \
--to=tytso@mit.edu \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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