All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] fix tool pygrub build on x64
Date: Mon, 16 May 2005 16:28:03 -0500	[thread overview]
Message-ID: <1116278883.4807.101.camel@thinkpad> (raw)
In-Reply-To: <20050516211310.GA15474@snarc.org>

Ok,
	To better followup my findings you will see that size_t is of type
__kernel_size_t. On i386 in "asm-i386/posix_types.h" you have:
typedef unsigned int    __kernel_size_t;

Where as on x86-64 you in "asm-x86_64/posix_types.h" you have:

typedef unsigned long   __kernel_size_t;

I must have typed "unsigned int" by accident. Sorry. But the fix is
still valid.

Where as in 
On Mon, 2005-05-16 at 23:13 +0200, Vincent Hanquez wrote:
> On Mon, May 16, 2005 at 02:15:33PM -0500, Jerone Young wrote:
> > 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".
> 
> size_t is "unsigned long" not "int"
> 
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

  parent reply	other threads:[~2005-05-16 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 19:15 [PATCH] fix tool pygrub build on x64 Jerone Young
2005-05-16 21:13 ` Vincent Hanquez
2005-05-16 21:22   ` Jerone Young
2005-05-16 21:33     ` Vincent Hanquez
2005-05-16 21:28   ` Jerone Young [this message]
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=1116278883.4807.101.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=vincent.hanquez@cl.cam.ac.uk \
    --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.