From: Jeff Dike <jdike@addtoit.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] compile problem
Date: Wed, 13 Feb 2008 12:43:18 -0500 [thread overview]
Message-ID: <20080213174318.GB12071@c2.user-mode-linux.org> (raw)
In-Reply-To: <47B20F0F.3050401@gmail.com>
On Tue, Feb 12, 2008 at 10:26:39PM +0100, Jiri Olsa wrote:
> <asm/types.h> declares u32 only if there's __KERNEL__ defined, which is not case
> of UML compile.
And anything else that uses ptrace.
> Now when I know why my Linus' tree wont compile, I'd like to know why yours does :)
Because you have this header installed as your system ptrace-abi...
> (I used your patch regarding the foo function errors as well...)
> Maybe I have smth wrong with my headers, I use following symlinks:
>
> /usr/include/linux -> $(kernel)/include/linux
> /usr/include/asm -> $(kernel)/include/asm-x86
This is the one - you're not supposed to do that any more. No distro
has done this in probably 10 years. You're supposed to use the
sanitized libc headers that come with your distro.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-02-13 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 20:06 [uml-devel] compile problem Jiri Olsa
2008-02-11 23:18 ` Jeff Dike
2008-02-12 21:26 ` Jiri Olsa
2008-02-13 17:43 ` Jeff Dike [this message]
2008-02-12 1:12 ` Jeff Dike
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=20080213174318.GB12071@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=olsajiri@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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