From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Breakage of compilation in .11-rc1 - "code-tidying" is broken
Date: Thu, 13 Jan 2005 20:08:41 +0100 [thread overview]
Message-ID: <200501132008.41725.blaisorblade@yahoo.it> (raw)
I've verified the compilation problem posted about -rc1:
arch/um/kernel/process.c: In function `check_ptrace':
arch/um/kernel/process.c:321: error: `PTRACE_SETOPTIONS' undeclared (first use
in this function)
arch/um/kernel/process.c:321: error: (Each undeclared identifier is reported
only once
arch/um/kernel/process.c:321: error: for each function it appears in.)
arch/um/kernel/process.c:321: error: `PTRACE_O_TRACESYSGOOD' undeclared (first
use in this function)
This is related to the TRACESYSGOOD patch and to an unverified patch, i.e. :
http://linux.bkbits.net:8080/linux-2.5/cset@41e49628dGbOWX-bT9yZII4f19GT6A
I.e, the "Code Tidying" patch still on the incrementals.
In fact, including both linux/ptrace.h and sys/ptrace.h is not redundant - it
must also be done in the proper order, so I'm writing a patch with the
appropriate content.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2005-01-13 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 19:08 Blaisorblade [this message]
2005-01-13 22:05 ` [uml-devel] Re: Breakage of compilation in .11-rc1 - "code-tidying" is broken Jeff Dike
2005-01-13 20:19 ` Blaisorblade
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=200501132008.41725.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.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