From: Jeff Dike <jdike@addtoit.com>
To: blaisorblade_spam@yahoo.it
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [patch 02/11] uml: fix compilation for missing headers
Date: Fri, 14 Jan 2005 14:22:20 -0500 [thread overview]
Message-ID: <200501141922.j0EJMKnV003227@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 13 Jan 2005 22:00:51 +0100." <20050113210051.99326AB30@zion>
blaisorblade_spam@yahoo.it said:
> If you think it cannot make sense to include both <sys/ptrace.h> and
> <linux/ptrace.h> (as userspace process, i.e. host includes), go
> complaining with glibc, or follow the linux-abi includes idea.
> However, the compilation failure is possibly glibc-version (or better
> glibc includes version) related - what I now is that the failure
> happens on my system with a glibc 2.3.4 (from Gentoo).
> Also, remove some syscalls from the syscall table, since some syscalls
> were added which are only inside -mm currently, and this prevents
> currently compilation.
Hold off on this one. I have different fixes for this in my tree.
The system ptrace headers (asm/ptrace.h, sys/ptrace.h, linux/ptrace.h) have
varying effects, depending on distro and architecture. So, I decided to put
sysdep/ptrace_user.h in charge of supplying the system ptrace information to
the rest of UML. This has some ripple effects which I am in the process of
sorting out.
On the system calls, I have them indef-ed depending on whether one of the
__NR_vperf symbols are defined. This will go away when the entry points
are in both -mm and -linus.
Jeff
prev parent reply other threads:[~2005-01-14 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 21:00 [patch 02/11] uml: fix compilation for missing headers blaisorblade_spam
2005-01-14 0:20 ` Blaisorblade
2005-01-14 19:22 ` Jeff Dike [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=200501141922.j0EJMKnV003227@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
--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