From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] fix tool pygrub build on x64
Date: Mon, 16 May 2005 14:15:33 -0500 [thread overview]
Message-ID: <1116270934.4807.92.camel@thinkpad> (raw)
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
This fixes tool pygrub to build on x86-64 systems. Currently gcc is
saying there are incompatible pointer type passed into function
ext2fs_file_read. The address of variable n is used in ext2fs_file_read
which takes an "unsigned int *" as the 4th variable. "n" is currently
declared as an "size_t" which is an "int". This declares n as an
"unsigned int" instead of using type "size_t".
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
[-- Attachment #2: pygrub_x64_patch.diff --]
[-- Type: text/x-patch, Size: 399 bytes --]
--- tools/pygrub/src/fsys/ext2/ext2module.c.orig 2005-05-16 13:41:31.833244872 -0500
+++ tools/pygrub/src/fsys/ext2/ext2module.c 2005-05-16 13:49:44.573336992 -0500
@@ -55,7 +55,7 @@ static PyObject *
ext2_file_read (Ext2File *file, PyObject *args)
{
int err, size = 0;
- size_t n, total = 0;
+ unsigned int n, total = 0;
PyObject * buffer = NULL;
if (file->file == NULL) {
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-05-16 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 19:15 Jerone Young [this message]
2005-05-16 21:13 ` [PATCH] fix tool pygrub build on x64 Vincent Hanquez
2005-05-16 21:22 ` Jerone Young
2005-05-16 21:33 ` Vincent Hanquez
2005-05-16 21:28 ` Jerone Young
2005-05-16 21:43 ` Vincent Hanquez
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=1116270934.4807.92.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.